zsh-workers
 help / color / mirror / code / Atom feed
From: Zefram <A.Main@dcs.warwick.ac.uk>
To: zsh-workers@math.gatech.edu (Z Shell workers mailing list)
Subject: A couple of queries
Date: Sun, 9 Jul 1995 05:28:18 +0100 (BST)	[thread overview]
Message-ID: <25792.199507090428@stone.dcs.warwick.ac.uk> (raw)

-----BEGIN PGP SIGNED MESSAGE-----

In glob.c, in the function file_type() (which contains the delightful
comment "screw POSIX"), there is commented-out code that would return a
character '&' instead of '@' for a symbolic link that doesn't point
anywhere accessible.  Considering that compatibility with "ls -F" isn't
really an issue here (and '%' and '#' are returned for devices which ls
doesn't do), why is this code not used?

Secondly, I had an idea for a new option for a couple of builtins.
compctl has an option -L that makes zsh output the actual compctl
commands that one would have to input in order to get to the current
set of completion options.  A similar option would be very useful for
alias, bindkey (especially), limit, sched and typeset.  (typeset -L is
already taken, so it would have to be something else, but the others
can be -L.)  These options would not only be useful in normal use of
the shell, but would also simplify the reporter script greatly (which
btw won't run here -- awk syntax errors).  This option could be added
to each of the builtins quite easily, and without (much) risk of
breaking anything else.  What are people's opinions on this idea?
Richard, would you be willing to add this to the baseline before the
2.7 release?

 -zefram

-----BEGIN PGP SIGNATURE-----
Version: 2.6.i

iQBVAgUBL/9a32WJ8JfKi+e9AQGF7AH9HAhCS6kfVrKN66tXP6mjG255v4GkEmAS
2Ffm2ABz/NS3YpuGkDBeAV7ZwagpCdVSJFFSlwQCZiW/zLioO4yt8A==
=M++8
-----END PGP SIGNATURE-----


             reply	other threads:[~1995-07-09  4:29 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1995-07-09  4:28 Zefram [this message]
1995-07-09  4:53 ` Richard Coleman
1995-07-09  5:47   ` Zefram

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=25792.199507090428@stone.dcs.warwick.ac.uk \
    --to=a.main@dcs.warwick.ac.uk \
    --cc=zsh-workers@math.gatech.edu \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.vuxu.org/mirror/zsh/

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).