| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The hardcoded subcommands array lists commands removed from Django
between 1.9 and 1.10 (reset, runfcgi, sql, sqlall, sqlclear,
sqlcustom, sqlindexes, sqlreset, syncdb, validate). The last Django
release that shipped these commands was 1.8, which reached end of
life in April 2018.
These entries cannot provide backward compatibility: the file also
parses manage.py --help at runtime, which would already surface them
on any Django version that still has them. On every modern Django
release, however, they appear as phantom entries that produce
"Unknown command" when selected.
Drop the list and rely entirely on the runtime parse. This eliminates
the maintenance burden that caused it to drift out of date.
|
| |
|
|
|
|
|
|
|
|
|
|
| |
Django groups subcommands by app and prints column-0 section headers
such as [auth], [contenttypes], [django]. The current awk filter only
drops lines before "Available subcommands" and strips the first two
characters of every subsequent line, so those headers survive as bogus
entries like "uth]", "jango]", "mber]", corrupting the completion list
and producing mangled columnar output.
Skip lines starting with "[" and only retain indented lines (the real
subcommand entries), stripping the leading whitespace.
|
| | |
|
| | |
|
| |
|
|
|
| |
'--newbuffer' was introduced since nano 9.2 and added as
better synonyms of '--multibuffer'.
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The original report states:
mkdir -p /tmp/x && cd /tmp/x && touch ab-xyFOO ac-xyBAR
cat -xy<TAB>
autocompletes to `aB-xy`, and
mkdir -p /tmp/t && cd /tmp/t && touch 1abc 2abc
cat a<TAB>
autocompletes to `Aabc`.
check_cmdata has already advanced md->str by md->len when sfx is true,
so doing it again here is incorrect. bld_line then wants a pointer to
the start of the string, so subtract the length when sfx is true, since
it is an end pointer in that case (as is done in many other places in
this function already).
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
| |
This also led me to discover that if you type a leading nul in zsh, it
passes through correctly to linux and it gives us an abstract socket
instead, so document that that works, and print them properly. Also add
support for reporting the autobind socket name if you pass an empty path.
The more specific size in the bind and connect calls is due to abstract
sockets using the entire specified length, regardless of any embedded 0
bytes.
|
| | |
|
| |
|
|
| |
Test changes here are for extra coverage, previous tests still pass
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
| |
This was introduced in 51404.
|
| | |
|
| | |
|
| | |
|
| |
|
|
| |
Includes unposted K01nameref test
|
| |
|
|
|
| |
This function is available since gdbm 1.13 and even debian old old
stable has 1.17, so this should be fine.
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The stated goal of FDT_MODULE is:
/*
* Entry visible to other processes but controlled by a module.
* The difference from FDT_EXTERNAL is that closing this using
* standard fd syntax will fail as there is some tidying up that
* needs to be done by the module's own mechanism.
*/
#define FDT_MODULE 3
but this wasn't actually enforced. By accident, some fds ended up as
FDT_INTERNAL because movefd clobbers the FDT_MODULE value and those were
protected from closing. I think this straightens out all the bits
properly, at least the ones I found.
(Note that zsocket is using FDT_EXTERNAL purposefully because the user
*is* expected to close those fds with the {myfd}>&- syntax, it has no
specific interface to close opened sockets since it has no internal
state for them.)
Both zsocket and ztcp forgot to movefd the some of their fds which meant
it was potentially in the 0-9 range, which is also not protected from
being closed by the user, but:
Since the -d flag allows the user to put module fds at low fds, I made
the check forbid closing FDT_MODULE fds in that range too, I think
that's correct?
zftp did some very questionable things, relying on FDT_UNUSED fds to act
approximately like it expected, instead use FDT_MODULE there too.
Also make redup ensure the fdtable is big enough for the assignments
after, just for consistency, since the old addmodulefd call before
didn't necessarily grow it to the moved-to fd number.
Remove some misleading comments like
/* move the fd since no one will want to read from it */
the reason we move the fd is because we have promised the user we will
not open fds in the 0-9 range.
Also added maximum macro, and converted existing users of MIN/MAX to
them, since we have not, as far as I can tell, made any effort to check
that those macros are in fact defined by anyone.
|
| | |
|
| | |
|
| |
|
|
|
| |
In particular, fc -P/-p didn't interact well with undo. Make sure we
store/restore histline across those calls.
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
