| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| | |
|
| |
|
|
|
|
|
|
|
|
|
| |
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.
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
| |
This was introduced in 51404.
|
| | |
|
| |
|
|
|
| |
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.
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
|
| |
oliver shared a user report that grep completion doesn't work properly
on macos any more. this is because it no longer uses gnu grep -- it's
been freebsd grep since at least 2019
there appear to be other inaccuracies in this function which we should
revisit, but this will solve the issue as reported
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
as mentioned in 54915:
_mac_files_for_application was previously used by _open to complete only
file types appropriate for an application. this ended up being annoying
in practice, especially with text editors, because they don't (can't)
actually enumerate all of the file types they support. so in w/43061 i
made _open stop using it
since then, there has been no need for this function, and atm i don't
foresee one in the future
therefore we can remove it
|
| |
|
|
|
| |
mikael pointed out that this failure message wasn't colourised like the
others and didn't use the same wording
|
| |
|
|
|
|
|
| |
- w/51142
- w/54893
- w/54912
- w/54913
|
| | |
|
| |
|
|
|
|
| |
also improve _retrieve_mac_apps
tweak: fix variable name left over from earlier revision
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
|
| |
% print -r - ${(q+):-foo = bar}|xxd
00000000: 2766 6f6f 208d 2062 6172 270a 'foo . bar'.
% print -r - ${(q+):-foo * bar}|xxd
00000000: 2766 6f6f 2087 2062 6172 270a 'foo . bar'.
% print -r - ${(qqqq):-foo = bar}
$'foo \215 bar'
|
| |
|
|
|
|
|
|
|
| |
tweaks:
- set bare_glob_qual per feedback from bart (w/54897)
- fix zle/bindkey loops per feedback from mikael
- glob with (oN) per feedback from oliver
- eliminate another loop
|
| |
|
|
|
|
|
|
|
|
| |
With the previous (and now fallback) version of checkptycmd(), doing
this:
zpty foo 'while read; do echo hi; done'
zpty (or zpty -t foo)
would hang forever, which seems counterintuitive to the purpose of
listing processes (or testing if a process is running).
|
| | |
|
| |
|
|
| |
zsh-completions (by Hydrargyrum)
|
| | |
|
| |
|
|
| |
and update callers
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
|
| |
re: previous commit, this one was actually ok since another option is
added in front of the -A on solaris. and the change was undesirable for
the iputils case since it uses the args array for options to _arguments
itself
|
| |
|
|
|
|
| |
specs beginning with -[AMO] must be guarded
also fix an erroneous -A option in _module-assistant
|
