Age | Commit message (Collapse) | Author |
|
* 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
|
|
|
|
|
|
|
|
If a zero-length match is found do the replacement and increment the start point
for the next search by one. This allows for commands like s/^/- /
This brings the behaviour closer to the way sed and vi work.
OK schwarze@
|
|
|
|
|
|
|
|
OK natano@, jmc@
(I forgot to commit it back in mid-August when it was discussed.)
|
|
This behavior already existed but was unintentionally lost in revision
1.70 of ps.c.
ok millert@ tb@
|
|
prompt for huge lines (according to otto this happens only when
BACKWARDS is not defined);
ok otto
|
|
from bytevolcano
ok millert
|
|
timed(8) support for date(1) was removed years ago.
ok millert@ deraadt@
|
|
tweaks and ok guenther
|
|
faster than the system is more of a caveat than a bug. The comment also
dates back to ye olden times when the information was collected via
multiple kvm reads. The sysctl interface provides a much more consistent
snapshot, albeit one that may be outdated by the time it's printed.
Reword accordingly.
|
|
|
|
magic number.
|
|
|
|
diff from Carlin Bingham. ok millert.
|
|
alphanumeric, spotted by and ok sthen
|
|
from daniel bolgheroni
|
|
ok nicm@
|
|
"complete_commandname_argnum", for example:
set -A complete_kill_1 -- -9 -HUP -INFO -KILL -TERM
To set completions for the first argument to kill(1). If no complete_*
arrays are present, the normal filename completion is offered.
positive comments from many; man page ok/tweaks jmc; ok tedu
|
|
|
|
|
|
|
|
noted by tb@
|
|
value that merits a warning in the manpage and using 2 billion will get
you practically the same effect, so delete the -E none support
|
|
reduce and sort #includes
|
|
|
|
<sys/time.h> is unnecessary; sort the #includes
|
|
|
|
<sys/time.h> and <unistd.h> are unnecessary, but <time.h> is; sort #includes
|
|
<sys/time.h>, <errno.h> and <unistd.h> are unnecessary; sort #includes
|
|
<sys/time.h> is unnecessary; sort #includes
|
|
|
|
<unistd.h> and <sys/time.h> are unneeded here
ok by general acclaim
|