zsh-users
 help / color / mirror / code / Atom feed
From: "Nadav Har'El" <nyh@math.technion.ac.il>
To: Dan Kenigsberg <danken@cs.technion.ac.il>
Cc: zsh-users@sunsite.dk
Subject: Re: newbie's question about completion
Date: Thu, 8 Nov 2001 14:35:15 +0200	[thread overview]
Message-ID: <20011108143515.A14099@leeor.math.technion.ac.il> (raw)
In-Reply-To: <200111081225.OAA22487@csd.cs.technion.ac.il>; from danken@cs.technion.ac.il on Thu, Nov 08, 2001 at 02:25:36PM +0200

On Thu, Nov 08, 2001, Dan Kenigsberg wrote about "Re: newbie's question about completion":
> This is SuSe 7.0 that has setopt recexact in its /etc/zshrc (arghhh).
> My problem had nothing to do with zsh versions..

I don't understand why distributions do this... Zsh has a set of defaults
and these are clearly explained in the manual; If a distribution overrides
this default, it leaves the user clueless why the behavior described in
the manual is not happening. And why do they think that their defaults
make more sense than the defaults decided upon by the zsh developers?

I recommend you send a bug report to SuSe and ask them to remove this
silly setting.

> Recently, I found a truer "bug" in SuSe's startup files: /etc/profile
> sets alias ls='eval /bin/ls $LS_OPTIONS'.
> Appart of the question whether it is sensible to expand $LS_OPTIONS every time
> you do ls, this distroys arguments with spaces. (confession: I do not fully
> understand why)

The "eval" indeed reparses the whole line and rebreaks it on spaces ($IFS,
actually)... What they probably meant to do was to only break LS_OPTIONS,
in which case they should do

	alias ls='\ls ${=LS_OPTIONS}'

(the ${=...} enables SH_WORD_SPLIT for this time only - see the zsh manual.
the \ls is used instead of /bin/ls to find ls wherever it is - not necessarily
/bin).

Of course, this solution works only in zsh, so it should be placed in
/etc/zprofile, not /etc/profile. Or use the solution you described which
works on any Bourne-like shell.

> (Nadav, it seems I'm following you everywhere..)

Don't you know that I subscribe to every mailing list in existance? :)

-- 
Nadav Har'El                        |   Thursday, Nov  8 2001, 22 Heshvan 5762
nyh@math.technion.ac.il             |-----------------------------------------
Phone: +972-53-245868, ICQ 13349191 |Despite the cost of living, have you
http://nadav.harel.org.il           |noticed how it remains so popular?


  reply	other threads:[~2001-11-08 12:35 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-11-08  9:37 Dan Kenigsberg
2001-11-08  9:46 ` Will Yardley
2001-11-08 11:01 ` Oliver Kiddle
2001-11-08 11:44   ` Dan Kenigsberg
2001-11-08 12:06     ` Nadav Har'El
2001-11-08 12:25       ` Dan Kenigsberg
2001-11-08 12:35         ` Nadav Har'El [this message]
2001-11-08 13:47           ` Vincent Lefevre
2001-11-08 13:56             ` Peter Stephenson
2001-11-08 14:35               ` Vincent Lefevre
2001-11-08 14:15             ` Mads Martin Joergensen

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=20011108143515.A14099@leeor.math.technion.ac.il \
    --to=nyh@math.technion.ac.il \
    --cc=danken@cs.technion.ac.il \
    --cc=zsh-users@sunsite.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).