zsh-workers
 help / color / mirror / code / Atom feed
From: Peter Stephenson <pws@ibmth.df.unipi.it>
To: zsh-workers@sunsite.auc.dk
Subject: Re: WORDCHARS, etc.
Date: Mon, 14 Jun 1999 16:42:29 +0200	[thread overview]
Message-ID: <9906141442.AA40274@ibmth.df.unipi.it> (raw)
In-Reply-To: "Sven Wischnowsky"'s message of "Mon, 14 Jun 1999 11:19:18 DFT." <199906140919.LAA28474@beta.informatik.hu-berlin.de>

Sven Wischnowsky wrote:
> I've prepared a patch for this argument-passing thing, too. I haven't
> tried, but I'm sure this will clash with Peter's patch. So I'll just
> explain what it does and append it below if some of you want to try
> it. Those parts that are considered good things can then be merged
> with Peter's.

I'd better leave both of these out of pws-22 and we can decide later.  No
doubt Bart will have impartial views.

> - The zle functions (the C-functions) have been changed to get an
>   `char **args' argument and to return an integer. The return value is 
>   currently only used to signal some kind of error condition. Of
>   course, it is also returned when invokiing widgets via `zle'.

This is more far-reaching than mine.

> - I've taken {vi-,}history-search-{for,back}ward as examples that use
>   the arguments -- they all accept one string which is then searched.

I just made it put the string given in the buffer, but your idea is
probably more useful, since mine doesn't lend itself to subsequent
programming.

> - The read builtin uses `getkey()' when called from a zle widget and
>   when reading from stdin.

is that when (called from a zle widget && reading from stdin)? in which
case that's a good idea.

> - Another option for `zle': -R makes the command line be re-displayed.
>   It gets an optional argument: a string to display in the status
>   line.

This is useful

> - Finally, my suggestion for enhancing aliases. I've used a different
>   option character for this and because I couldn't think of a good
>   one, I've just taken `X':
> 
>     zle -X new-name old-name numeric args...

I'm not sure we need both this and zle -A.  And having this the other way
round from zls -A is just creating more confusion, even if the -A choice
was non-optimal (though it is in the UNIX tradition of things like mv and
ln; if -L hadn't been used it would have been more obvious).

There was some opposition to enhancing aliases anyway, since you can
always define a function widget.  One reason why I like them is it raises
the possibility of having builtin widgets implemented as aliases at shell
startup, which is a non-starter if you need a function.

-- 
Peter Stephenson <pws@ibmth.df.unipi.it>       Tel: +39 050 844536
WWW:  http://www.ifh.de/~pws/
Dipartimento di Fisica, Via Buonarroti 2, 56127 Pisa, Italy


  reply	other threads:[~1999-06-14 15:11 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-06-14  9:19 Sven Wischnowsky
1999-06-14 14:42 ` Peter Stephenson [this message]
  -- strict thread matches above, loose matches on Subject: below --
1999-06-15  6:57 Sven Wischnowsky
1999-06-14 13:12 Sven Wischnowsky
     [not found] <199906101042.MAA23616@beta.informatik.hu-berlin.de>
1999-06-12 15:41 ` Peter Stephenson
1999-06-13  6:53   ` Wayne Davison
1999-06-13 11:17     ` Bart Schaefer
1999-06-14  7:15       ` Peter Stephenson

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=9906141442.AA40274@ibmth.df.unipi.it \
    --to=pws@ibmth.df.unipi.it \
    --cc=zsh-workers@sunsite.auc.dk \
    /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).