zsh-workers
 help / color / mirror / code / Atom feed
From: Bart Schaefer <schaefer@brasslantern.com>
To: Jordan Russell <jordan.likes.curry@gmail.com>
Cc: "Jun. T" <takimoto-j@kba.biglobe.ne.jp>,
	Zsh hackers list <zsh-workers@zsh.org>
Subject: Re: _time_zone gives me candidates other than timezones
Date: Wed, 6 Apr 2022 13:11:38 -0700	[thread overview]
Message-ID: <CAH+w=7YLPLqgOcm6eiGKA67SHnWTR+ESm9c3r7G+L_=hTZ2yiw@mail.gmail.com> (raw)
In-Reply-To: <87bkxfw24f.fsf@smokey>

On Tue, Apr 5, 2022 at 4:19 PM Jordan Russell
<jordan.likes.curry@gmail.com> wrote:
>
> I like Jun's solution.

That's good, because it's already been added to the repository.
However, I did notice that if one explicitly attempts to start a
timezone name with "z" or "l", the lower case file names are in fact
offered (instead of, for example, correcting to Zulu).

> I still have reservations about completing right/
> and posix/ (they could be flags instead to the calling program).

Do you mean the calling program might use those as keywords (with no
leading hyphen[s])?  Or do you mean the caller of _time_zone should
[be able to] specify whether to include them?

> >I guess it comes down to whether you call _time_zone to find a zoneinfo
> >/file/ or a timezone /name/.
[...]
> > But if you're completing filenames you'd also need to recover
> >the prefix which is lost when using -W as is used now.

Further, if you start completing the tail of an absolute path, normal
file completion occurs.


  reply	other threads:[~2022-04-06 20:12 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-24 18:36 Jordan Russell
2022-03-29 23:22 ` Bart Schaefer
2022-03-30  0:12   ` Aaron Schrab
2022-03-31 15:25     ` Jun. T
2022-04-05 23:18       ` Jordan Russell
2022-04-06 20:11         ` Bart Schaefer [this message]
2022-04-08  7:30           ` Jun T

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='CAH+w=7YLPLqgOcm6eiGKA67SHnWTR+ESm9c3r7G+L_=hTZ2yiw@mail.gmail.com' \
    --to=schaefer@brasslantern.com \
    --cc=jordan.likes.curry@gmail.com \
    --cc=takimoto-j@kba.biglobe.ne.jp \
    --cc=zsh-workers@zsh.org \
    /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).