zsh-users
 help / color / mirror / code / Atom feed
From: Ray Andrews <rayandrews@eastlink.ca>
To: zsh-users@zsh.org
Subject: Re: symlink chain.
Date: Sat, 03 Jan 2015 19:35:10 -0800	[thread overview]
Message-ID: <54A8B4EE.30908@eastlink.ca> (raw)
In-Reply-To: <150103164002.ZM23676@torch.brasslantern.com>

On 01/03/2015 04:40 PM, Bart Schaefer wrote:
> My actual view is closer to the pocketknife than to the wrench.  The
> -w and -s options of whence can be useful with a full path.  The -m
> option just isn't that sort of blade.

I think the core of the difference between our points of view, is that 
for me, it's a simple question of trying to maximize consistency and 
minimize surprise.  For you,
knowing the guts of how these things work, it is intuitive/obvious that 
-m should do what it  does, and not work with full paths, whereas for 
me, not knowing that stuff, I take the more superficial view and don't 
want -m killing a search that would work fine without it.  I expect -m 
to *just* *add* the ability to search for patterns, not to kill 
otherwise acceptable searches. When I know how this hash table works, I 
will probably come round to your way of viewing it.
> Don't use the knife with both ends unfolded and then complain when you
> stab yourself in the thumb.
>

Well, one analogy is as good as another.  With so many of these issues, it
comes down to how you look at it.  For me, switches add features, they
don't invalidate arguments ... but is that really a rule? ...
> However, if you REALLY want the -m option to do something special with
> arguments that start with a slash, you need this (which I won't commit):
>

As we were saying it's not really about the slash, I'd say it's more a 
test for an existing, specific file, no?  FWIW, this is  how I handle it 
now:


      local ma=ma
       [ -e $1 ] && ma=
       find_count=`whence -$ma "$nnocase$1" | wc -l`

... pretty sad, IMHO, I do what whence should do for me, and cut out the 
-ma when
they are going to sabotage the output.  Anyway, it works fine, it just 
bugs me.


I hafta learn how to do this patching (I don't want to blow something up 
doing it wrong) and I have to learn how to ask git to preserve any local 
changes while still
pulling whatever needs to be pulled.  (Most cool that it can do that 
sort of thing at all.)  You can't sneak anything past git, that's for sure.


> diff --git a/Src/builtin.c b/Src/builtin.c
> index ebc0654..509629f 100644
> --- a/Src/builtin.c
> +++ b/Src/builtin.c
> @@ -3243,10 +3243,28 @@ bin_whence(char *nam, char **argv, Options ops, int func)
>   	    }
>   	    /* Done search for `internal' commands, if the -p option *
>   	     * was not used.  Now search the path.                   */
> -	    cmdnamtab->filltable(cmdnamtab);
> -	    scanmatchtable(cmdnamtab, pprog, 1, 0, 0,
> -			   (all ? fetchcmdnamnode : cmdnamtab->printnode),
> -			   printflags);
> +	    if (**argv == '/') {
> +		if (all)
> +		    addlinknode(matchednodes, *argv);
> +		else if ((cnam = findcmd(*argv, 1))) {
> +		    /* Found external command. */
> +		    if (wd) {
> +			printf("%s: command\n", *argv);
> +		    } else {
> +			if (v && !csh)
> +			    zputs(*argv, stdout), fputs(" is ", stdout);
> +			zputs(cnam, stdout);
> +			if (OPT_ISSET(ops,'s') || OPT_ISSET(ops,'S'))
> +			    print_if_link(cnam, OPT_ISSET(ops,'S'));
> +			fputc('\n', stdout);
> +		    }
> +		}
> +	    } else {
> +		cmdnamtab->filltable(cmdnamtab);
> +		scanmatchtable(cmdnamtab, pprog, 1, 0, 0,
> +			       (all ? fetchcmdnamnode : cmdnamtab->printnode),
> +			       printflags);
> +	    }
>   
>   	    unqueue_signals();
>   	}
>


  reply	other threads:[~2015-01-04  3:35 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-12-27  4:50 Ray Andrews
2014-12-27 23:38 ` Ray Andrews
2015-01-02 17:03 ` Peter Stephenson
2015-01-02 18:42   ` Ray Andrews
2015-01-02 20:27     ` Lawrence Velázquez
2015-01-02 21:19       ` Ray Andrews
2015-01-02 21:24     ` Peter Stephenson
2015-01-02 21:36       ` Ray Andrews
2015-01-02 21:53       ` Ray Andrews
2015-01-02 22:21         ` Peter Stephenson
2015-01-02 23:42           ` Ray Andrews
2015-01-03  1:08             ` Ray Andrews
2015-01-03  5:03               ` Bart Schaefer
2015-01-03  5:53                 ` Ray Andrews
2015-01-03  7:17                   ` Bart Schaefer
2015-01-03 17:14                     ` Ray Andrews
2015-01-03 20:02                       ` Bart Schaefer
2015-01-03 21:13                         ` Ray Andrews
2015-01-03 21:42                           ` Peter Stephenson
2015-01-03 22:42                             ` Ray Andrews
2015-01-04  0:41                               ` Bart Schaefer
2015-01-04  3:45                                 ` Ray Andrews
2015-01-04  0:40                           ` Bart Schaefer
2015-01-04  3:35                             ` Ray Andrews [this message]
2015-01-04  8:31                               ` Bart Schaefer
2015-01-04 20:49                                 ` Ray Andrews
2015-01-05  1:34                                   ` Bart Schaefer
2015-01-05  2:28                                     ` Lawrence Velázquez
2015-01-05  4:24                                       ` Ray Andrews
2015-01-02 22:22         ` Bart Schaefer

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=54A8B4EE.30908@eastlink.ca \
    --to=rayandrews@eastlink.ca \
    --cc=zsh-users@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).