Age | Commit message (Collapse) | Author |
|
passing empty format strings to printf-family functions; ok millert@
|
|
not just the first one that matches. OK deraadt@
|
|
|
|
|
|
|
|
noted by scott cheloha
|
|
|
|
ok guenther
|
|
ok kettenis
|
|
minek van on misc@. Thanks.
ok tb@, tj@
(and jmc@ is ok with the diff but can't ok the technical content).
|
|
and simplify the next sentence; triggered by a different patch
from Anton dot Lindqvist at gmail dot com.
OK millert@ tb@
|
|
ok ajacoutot@
|
|
flag to fts_open led to the following behavior: the symlink's permissions
were read, changed according to the command line, and transferred to the
target file. chflags had a similar problem while chmod was unaffected.
Regression introduced in r1.33. Reported by Christopher Wellons, thanks!
ok guenther
|
|
|
|
of "tape" for a week or so.
|
|
but avoids doing pledge "tty" operations against flat files. The shell's
tty will be kind of special in the near future. isatty is also a lot less
kernel code to run through the loop.
|
|
upon "inet". Adjust the 4 programs that care about this.
|
|
found. Makes gcc happier. Add __dead to function prototype as we
go by.
ok guenther@
|
|
"warning:" rectification.
|
|
as per POSIX. With this patch, ",n" is an abbreviation for "1,n",
";n" abbreviates ".;n". The "n," and "n;" variants mean "n,n" and "n;n",
respectively.
Patch from Jerome FRGAGIC; ok stefan, deraadt
|
|
so gcc doesn't complain about defining but not using them.
typo correction & ok jca@
|
|
prompt. From NetBSD.
ok millert@, deraadt@
|
|
turn is inside an #ifdef. Thus making the code clearer by eliminating
an #ifdef in the middle of the declarations.
Suggested by millert@
|
|
adding appropriate #ifdef's around declarations.
ok millert@ (with a tweak I will commit separately)
|
|
|
|
short-circuited `&&` or `||` chain in later iterations of `for`
loops. It should be disabled after a short-circuited `&&` or `||`
chain only in the *final* iteration of loops (as well as in
conditionals, which was already working). From Kartik Agaram.
|
|
so there is no need to check xerrorok for NULL after that.
From Kartik Agaram.
|
|
braces for improved readability. Based on a diff from Kartik Agaram.
|
|
ok mikeb@
|
|
distance from 'Ar command'.
This is schwarze's correct version of an initial incorrect diff from me.
|
|
1. Mark up reserved words intended to appear at the beginning of command
lines with .Ic.
2. Mark up syntax elements intended to appear in the middle of command
lines with .Cm.
This is not only more systematic, but also makes internal search
commands like :tif<enter>, :tstop<enter>, and :t[[<enter> work in
man(1).
|
|
|
|
The lack of this entry was reported by Jan Stary <hans at stare dot cz>.
OK czarkoff@ jmc@
|
|
* Consistently use "character encoding locale" as suggested by stsp@.
* Resolve various gratuitious wording variations.
OK jmc@.
|
|
Triggered by a different patch from Michal Mazurek.
Joint work by tb@, jmc@, and tedu@, but no one ever committed it.
|
|
Minor cleanup while here: return from main, static void __dead usage, etc.
Based on a patch from Jan Stary <hans at stare dot cz>.
Feedback and OK tb@, OK millert@.
|
|
OK nicm@ tb@ czarkoff@
|
|
no functional change; suggested by tb@
|
|
* It was only used in vi input mode.
* No functional change in case of set -o vi-show8.
* No functional change if LC_CTYPE is set to UTF-8.
* More robust for the default of LC_CTYPE=C on a UTF-8 xterm.
Behaviour changes for the combination LC_CTYPE=C with set +o vi-show8
on non-UTF-8 terminals, but that combination is useless and dangerous
with or without this patch. If you want to edit individual raw non-ASCII
non-UTF-8 bytes on the shell command line, always use set -o vi-show8.
(Besides, i doubt that you actually want to do that; better use a real
hex editor in the first place.)
OK czarkoff@.
|
|
and not to a continuation byte for these commands: b B e E w W |
Let {e,E}ndword return the position after the word because that is
easier to handle in the caller.
OK tb@ czarkoff@
|
|
from ray lai
|
|
jmc@ finds the key binding stuff "disgusting" (i can't argue with that)
and doesn't want to comment on the content, but agrees with the wording.
|
|
noticed by Jan Stary <hans at stare dot cz>;
return from main while here;
feedback and OK tb@, OK martijn@
|
|
so far, it covers these commands: a h i l x /
This is an isu8cont()-based hack similar in style to what i did
in emacs input mode, but less elegant and slightly more intrusive
because the vi mode code is much more ugly and less straightforward
than the emacs mode code. This one required partial rewrites of
a few helper functions, and comments were added while there.
This is not perfect, but hopefully reduces people's cursing
until a more rigorous solution can be devised (much) later.
Some polishing may be useful in tree, in particular adding
utf8cont() support to a few missing commands.
Mostly written shortly after Christmas 2015.
Reminded by and OK czarkoff@.
Feedback, partial review and testing, no longer any objection by martijn@.
Feedback and testing by tb@.
Also read fine to nicm@.
|
|
|
|
Found because of a hint by and OK schwarze@.
|
|
remove more dead code
|
|
|
|
|
|
|