| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
|
| |
I was hoping that a superoptimiser would help me find a miraculous
branchless equation to cover it, but in the end the branching
doesn't hurt at all in our case.
It's more readable than `(((char >> 2) - 0x38) & 0x60) ^ char`
or `(char ^ 0x40) & (((char >> 1) ^ 0x20) | 0x5f)`.
|
|
|
|
| |
Add an explanatory link, so that I don't need to look it up again.
|
|
|
|
| |
Regression introduced by cc59fcf.
|
|
|
|
| |
And document this feature in the manual page.
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
For more info, see e.g.
https://github.com/asciidoc/asciidoc-py3/issues/137
I'll probably commit to mandoc here but scdoc is appealing.
Somewhat sadly, it explicitly suppresses sentence spacing
but I'm wondering whether it couldn't be reimplemented better,
in a more AsciiDoc-like fashion.
|
|
|
|
| |
Yet, this program remains fairly unportable.
|
| |
|
| |
|
|
|
|
| |
Closes #1
|
|
|
|
| |
I've put the project in AUR, it seems to deserve it.
|
|
|
|
| |
I'm not particularly happy to write in mdoc but here goes.
|
|
|
|
| |
Since we have a version number at all, even if it's meaningless.
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
We can happily stick to POSIX and the usual variable names,
with the following exceptions:
- pkg-config(1) is used to find libraries and compile flags
- the new "static" target uses non-standard compiler
and linker flags, though it's not the default target
sdn is predestined for wild distribution,
even the dynamically linked libc is rather suboptimal.
|
|
|
|
|
|
| |
The wchar_t variant of compute_width() is no longer needed.
So all in all the better help has saved code.
|
|
|
|
| |
Considerably more useful and concise.
|
|
|
|
|
|
| |
Taken from Windows Explorer, which previously used Backspace.
We might want to use h/l for parent/choose by default.
|
|
|
|
|
|
| |
We do get these as a key, after all.
Closes #4
|
|
|
|
|
|
| |
Not completely happy with the explicit `halfdelay (1)`.
Updates #4
|
|
|
|
| |
Updates #4
|
| |
|
|
|
|
|
|
|
| |
Not caring about C-d right now, we might have to convince the tty
to send it to us--I'm not sure if it does, or returns EOF.
Updates #4
|
|
|
|
| |
Updates #4
|
|
|
|
|
|
| |
They might not be even printed correctly, though.
Updates #4
|
|
|
|
| |
Updates #4
|
| |
|
|
|
|
|
|
|
|
| |
Copying snippets from the README was uncomfortable and laborious,
and wasted a lot of space in the document, especially after
the recent additions.
Closes #3
|
|
|
|
| |
Word expansion is not performed there.
|
|
|
|
| |
Bash is a bad citizen but this order makes more sense.
|
|
|
|
|
|
| |
See Midnight Commander commit 436296f, blindly trusting it.
wc(1) could be used unconditionally but let's make it clear.
|
|
|
|
|
| |
In the end, we don't need to impose any policy on it,
and it removes a level of quoting, as well as an `eval`.
|
|
|
|
|
|
|
|
|
|
|
|
| |
SIGTSTP is sent to the entire foreground process group,
so do the some with our SIGCONT.
Debian's default sh (dash) doesn't replace itself with
the command, even if it's the last one in the -c option.
Of course, we do not need to use /bin/sh for the helpers
at all, though it doesn't cost us much. We could also
issue an explicit `exec`.
|
| |
|
|
|
|
| |
And in general fix all CTRL processing to handle the DEL character.
|
|
|
|
|
|
|
|
|
|
| |
And remove it from the "similar software" section.
Our relationship has progressed.
Other unusual shells I've checked before I gave up:
- nushell lacks the ability to bind keys to user functions
- yash can but is otherwise way too basic
|
|
|
|
|
|
|
|
|
| |
zsh's antisocial behaviour was fairly promptly fixed (thanks to
Stephane Chazelas and his patience).
zle-line-init and zle-line-reset seem to be user-defined widgets
and the order inverted. Put zle-line-init before reset-prompt
because some people do weird things in there.
|
|
|
|
|
| |
All the omitted error checking sometimes sucks a lot,
and I need to include it later anyway.
|
| |
|
|
|
|
|
|
|
|
| |
There's a slight issue with the inverted cell representing
the cursor standing out a bit too much amongst the rest of
the characters.
The resulting experience is a lot more consistent, though.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Since I'm already dealing with the fish shell.
All of our supported shells seem to handle cursor position
in Unicode (wide character) codepoints.
It was easiest and most straight-forward to pass the data
through yet-unused program arguments.
The cursor position is marked by a Unicode glyph equivalent
to ACS_DIAMOND, although ncurses doesn't get a chance
to make any ACS translation.
|
|
|
|
|
| |
I've also tried tcsh but while it /can/ be used for directory
navigation, it has several issues that are much more serious.
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
That is, if it's missing from our history.
This makes for a more consistent experience when traversing
the filesystem. Arguably, it's only good for when 'h' is
bound to the 'parent' action.
Also make sure that the offset and cursor are reset when
the path is changed.
|