zsh-workers
 help / color / mirror / code / Atom feed
From: Peter Stephenson <pws@ibmth.df.unipi.it>
To: zsh-workers@sunsite.auc.dk
Subject: Re: PATCH: _long_options
Date: Mon, 08 Mar 1999 12:15:41 +0100	[thread overview]
Message-ID: <9903081115.AA35710@ibmth.df.unipi.it> (raw)
In-Reply-To: "Sven Wischnowsky"'s message of "Mon, 08 Mar 1999 11:31:42 NFT." <199903081031.LAA11761@beta.informatik.hu-berlin.de>

Sven Wischnowsky wrote:
> I had this idea when playing with `_tar' (which is not changed, yet):
> there we probably should try to turn the archive name into a absolute
> path when building the cache name. Would
> 
>   tf="$PWD/$tf"
>   tf="${${tf//.\\/}//\\/[^/]#\\/..}"
> 
> be enough for that? (Looks funny, doesn't it? ;-)

Might be safer to leave ..'s in there, since they can do funny things.  Or
only replace them at the start of the old tf, where the user's intention is
probably clear.  Or something.

There's one other thing _tar probably ought to do... well, two other
things... well among the other things _tar ought to do which conceivably I
could possibly get around to doing when I'm feeling like it...

- in principle, you can have combined short arguments like -xv or -cP or
whatever anywhere on the command line before the file list, so it probably
ought to check if it had no luck early on --- e.g. look for
-[[:alpha:]]#[cxturA]*

- any --use-compress-program=*, or indeed --use-comp*, should get added to
$largs

- any --dir*=* should be changed to when completing archives and existing
files, which is another good argument for using absolute paths for $tf.

-- 
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-03-08 11:32 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-03-08 10:31 Sven Wischnowsky
1999-03-08 11:15 ` Peter Stephenson [this message]
1999-03-08 14:27   ` PATCH: _tar, again Peter Stephenson
  -- strict thread matches above, loose matches on Subject: below --
1999-03-08 10:03 PATCH: _long_options Sven Wischnowsky

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=9903081115.AA35710@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).