| Commit message (Collapse) | Author | Age |
|---|
| ... | |
| | | | |
|
| | | | |
|
| | | | |
|
| | | | |
|
| | | | |
|
| | | | |
|
| | | | |
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
hilex is meant to replace hi, based on lex rather than a mess of
overlapping regexps. I want to preserve hi's tagging abilities, but that
will require some amount of parsing/post-processing, which I'm not sure
how to approach yet.
Macro lexing for C still needs work, as I want to match strings and
comments inside macros.
|
| | | | |
|
| |\ \ \
| | | |
| | | |
| | | |
| | | |
| | | | |
git-subtree-dir: doc/zlib
git-subtree-mainline: db652695744cc54584296b54289166b4b21ac407
git-subtree-split: 38f010d3972db4262e7e0bcd7d6b9814f95d3538
|
| | | | | |
|
| | / / |
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Branches are grouped into their own section to make the "this commit"
option visually distinct.
Adding this option will result in two options being marked as selected
if a branch has the same name as a commit oid. But that would cause
all sorts of other problems anyway (attempting to switch to the branch
would actually give you the commit, etc.), so let's not worry about
that.
A "permalink" link on the blob view next to the "plain" link would
probably be more discoverable, but that would only work for the blob
view. The switch UI is visible everywhere.
Signed-off-by: Alyssa Ross <hi@alyssa.is>
|
| | | | |
|
| | | |
| | |
| | |
| | |
| | | |
Add links to symbolic link targets in tree listings, formatted like
"ls -l". Path normalization collapses any ".." components of the link.
|
| | | | |
|
| | | | |
|
| | | |
| | |
| | |
| | | |
This avoids piping binary blobs through the source-filter.
|
| | | | |
|
| | | | |
|
| |\| |
| | |
| | |
| | |
| | |
| | | |
'www/git.causal.agency/cgit'
From tag 'v1.2.3'.
|
| | /
| |
| |
| |
| | |
git-subtree-dir: www/git.causal.agency/cgit
git-subtree-split: 02221fd3fe523a3293d64e3359036e3a71d6fd7e
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
| | |
| |
| |
| |
| |
| | |
editline does not render a multi-line PS1 correctly when RPS1 is also
set. To work around this, return only the last line of the cached prompt
to editline, and print the leading lines separately inside setprompt.
|
| | | |
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Previously, the prompt would be expanded every time editline called the
getprompt callback. I think the code may have been written assuming that
editline only calls getprompt once per prompt, but it may actually call
it many times, for instance every time you type backspace. This results
not only in slower editing from expanding complex prompts repeatedly, it
also consumes more and more stack memory each time getprompt is called.
This can be seen by setting PS1 to some command substitution, typing
many characters at the prompt, then holding backspace and observing
memory usage. Thankfully all this stack memory is freed between prompts
by the stackmark calls around el_gets.
This change causes prompt expansion to always happen in the setprompt
call, as it would when editline is disabled, and a cached copy of the
prompt is saved for getprompt to return every time editline calls it.
Since getprompt is no longer doing expansion, the stackmark calls
surrounding el_gets can be removed.
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Check if the FreeBSD (and by extension macOS) _el_fn_sh_complete version
of the function exists, which does shell escaping of completed filenames
before _el_fn_complete learned to.
Tab is bound after calling el_set() and el_source() since the default
bindings set tab to something else, and it should always be filename
completion in the shell.
|
| | | |
|
| | |
| |
| |
| |
| | |
Previously, configure --with-libedit would only fail in the case where
libedit is available but its header file histedit.h is not.
|
| |\|
| |
| |
| | |
From tag 'v0.5.11.2'.
|
| |
|
|
|
| |
git-subtree-dir: bin/dash
git-subtree-split: a45870f71f42be6bf3c8eada04debd1008f9dc3e
|
| |
|
|
|
| |
Otherwise macOS gets very mad as it tries to access a bunch of protected
directories.
|
| |
|
|
| |
This fixes pressing K on "RFC3501", for example.
|
| |
|
|
|
| |
That default path is a bit wonky, but it prevents having to template
rfc.vim for basically no reason.
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
| |
Uninstalled TF2 and upgraded to macOS Catalina which can't run it ever
again. Goodbye TF2, you used to be fun.
|
| |
|
|
|
| |
Some RFCs reference other sections like "(Section 1.2)", where the
section header says "1.2.".
|
| | |
|
| |
|
|
| |
This removes any leading zeros such as in rfc-index.txt.
|
| | |
|
| |
|
|
|
| |
This supposedly lets vim do binary search on the file, not that it
seemed slow before. Also handle section headings with no names.
|
| | |
|
| | |
|
| |
|
|
|
|
| |
This sets iskeyword so that ^] will work for the kinds of tags generated
by rfctags.pl, and keywordprg so that K on another RFC number will view
that one. It also binds gO to jump to the table of contents of the RFC.
|