| Age | Commit message (Collapse) | Author |
|---|
|
From Scott Cheloha
ok tb@
|
|
|
|
and is not an easy fix for now.
|
|
borrowed from ksh93.
Survived a ports build performed by naddy@ and encouraged by many.
|
|
Sounds good to deraadt@
OK anton@
|
|
now.
ok schwarze@
|
|
complete UTF-8 character first. Fixes an issue while running ksh in tmux where
UTF-8 characters inserted in columns other than the last one are discarded.
With help from nicm@ and schwarze@ who also wrote the UTF-8 validation, thanks!
ok schwarze@
|
|
mode, not "stuff". While here, remove the poorly described "stuff"
and "stuff" bind functions as well..
In the unlikely event anyone has those in .kshrc, they'll need to
be removed.
ok anton@
|
|
What is not so simple is squinting hard enough to conclude that POSIX
actually says that. I'm still not sure how to do that.
Problem with the shell manual pointed out by "Choose a display name".
ok otto, halex, jmc
|
|
characters are involved; similar to what anton@ previously did for 'r';
OK tb@ anton@;
also tested by Walter Alejandro Iglesias <wai at roquesor dot com>.
|
|
Reported by Walter Alejandro Iglesias on tech@.
ok schwarze@ tb@
|
|
tendency for corruption to a simpler plaintext version.
To convert your current ksh history to plaintext, issue
fc -ln 1 | sed 's/^ //' > ~/ksh_hist.txt
before upgrading and use ksh_hist.txt as HISTFILE after the upgrade.
Original patch by marco in 2011. Ported to current during g2k16 by me.
Testing, bugfixes and improvements in joint work with natano.
Additional testing by anton and mestre. Includes some tweaks by anton.
Committing now to shake out remaining bugs before 6.2 is cut.
ok deraadt, mestre, anton, sthen
|
|
While here, remove a condition that becomes redundant.
ok schwarze@ tb@
|
|
requested by a mail on misc, via otto;
ok otto
|
|
in two respects:
1. During output in x_e_putc(), when counting display columns,
skip UTF-8 continuation bytes. Fixes backward movements that
cause horizontal scrolling.
2. After deleting characters, recalculate the last byte that fits
on the line.
Patch from <Anton dot Lindqvist at gmail dot com> on tech@.
OK millert@ tb@
|
|
|
|
warning from clang.
|
|
|
|
noted by scott cheloha
|
|
|
|
and simplify the next sentence; triggered by a different patch
from Anton dot Lindqvist at gmail dot com.
OK millert@ tb@
|
|
|
|
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.
|
|
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).
|
|
|
|
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.
|
|
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@.
|
|
|
|
|
|
OK natano@, jmc@
(I forgot to commit it back in mid-August when it was discussed.)
|
|
|
|
magic number.
|
|
|
|
alphanumeric, spotted by and ok sthen
|
|
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
|
|
OK deraadt@
|
|
other edge cases found by gsoares@. OK tb@ gsoares@
|
|
when ksh is compiled with -Os (done in distrib/special): move the
bit using XPptrv(l) (which expands to l.beg) where it is actually
used and clearly initialized.
ok tedu, tweak + ok millert
|
|
|
|
make commands starting with the escape key (^[) work as documented.
Long-standing bug, this time reported by Dave minus Cohen dot com.
OK natano@ halex@
|
|
that i misunderstood something when i wrote it;
found by guenther and naddy
|
