Newbie zsh setup warts (history, pipes, export, ...).

Newbie zsh setup warts (history, pipes, export, ...).

[s. keeling]

I'm uset to doing "set | grep -i blah" but in zsh that produces:

  Binary file (standard input) matches

"set | less" works.  What's wrong with the grep?

I also don't appear to have history set up correctly.  It's not
saving my history between sessions.  These are in my ~/.zshenv:

  -------------------------------
HISTCONTROL=ignoredups
HISTFILE=$HOME/.zsh_history
HISTSIZE=2000
setopt HIST_EXPIRE_DUPS_FIRST
setopt APPEND_HISTORY
setopt hist_verify
setopt extended_history

export        HISTCONTROL         \
              HISTFILE            \
              HISTSIZE
  -------------------------------

What am I missing here, and does zsh need those last three exported?


-- 
Any technology distinguishable from magic is insufficiently advanced.
(*)               http://www.spots.ab.ca/~keeling 
- -

Re: Newbie zsh setup warts (history, pipes, export, ...).

[Clint Adams]

> "set | less" works.  What's wrong with the grep?

grep is probably seeing the NUL character in IFS, and assuming.
that the input is "binary".  Since you're using GNU grep, you can
specify "grep -a" to override this assumption.

> HISTCONTROL=ignoredups
> HISTFILE=$HOME/.zsh_history
> HISTSIZE=2000
> setopt HIST_EXPIRE_DUPS_FIRST
> setopt APPEND_HISTORY
> setopt hist_verify
> setopt extended_history

You're missing SAVEHIST.

Re: Newbie zsh setup warts (history, pipes, export, ...).

[Bart Schaefer]

On Sun, 24 Oct 2004, s. keeling wrote:

> I also don't appear to have history set up correctly.  It's not
> saving my history between sessions.  These are in my ~/.zshenv:
> 
>   -------------------------------
> HISTCONTROL=ignoredups

This is only used by bash2.  You need "setopt HIST_IGNORE_DUPS" to get the 
zsh equivalent.  But if history ignores dups, then this ...

> setopt HIST_EXPIRE_DUPS_FIRST

... is a no-op, because there won't be any dups to expire.

> export        HISTCONTROL         \
>               HISTFILE            \
>               HISTSIZE
>   -------------------------------
> 
> What am I missing here, and does zsh need those last three exported?

No, they don't need to be exported, the latter two just need to be set. 

(It doesn't do any good to both export them and set them in ~/.zshenv, 
because every zsh will re-read ~/.zshenv and clobber the environment 
value.  You'd only export them if e.g. they were set in ~/.zlogin, which 
is not read by non-login shells.)

Clint answered the "missing" part.

Re: Newbie zsh setup warts (history, pipes, export, ...).

[s. keeling]

Incoming from Danek Duvall:
> > I'm uset to doing "set | grep -i blah" but in zsh that produces:
> > 
> >   Binary file (standard input) matches
> 
> Probably because IFS contains a NUL character (and you're using GNU grep).
> You could use the -a option to grep to force it to assume the input is

Thanks.  That works.

> > HISTCONTROL=ignoredups
> 
> No idea what this is; someone else might answer.

It could be a holdover from bash.

> > HISTFILE=$HOME/.zsh_history
> > HISTSIZE=2000
> 
> You also need SAVEHIST=xxx.  HISTSIZE is the size of the history any zsh

Ah!  Marvy.  I'll test that out.

> > export        HISTCONTROL         \
> 
> No, you shouldn't need to do that; they're shell variables, not environment
> variables, and so don't need to be exported.  I assume, but I'm not sure,
> that if you export them, subshells will pick up those values.  But my .z*

I'm not sure I understand the distinction between shell and env. vars,
but usually yes, exporting them makes them available to sub/child
processes.  At least that's what they're for in sh and bash.

Thanks everyone.


-- 
Any technology distinguishable from magic is insufficiently advanced.
(*)               http://www.spots.ab.ca/~keeling 
- -

Re: Newbie zsh setup warts (history, pipes, export, ...).

[Wayne Davison]

On Sun, Oct 24, 2004 at 06:11:16PM -0700, Bart Schaefer wrote:
> You need "setopt HIST_IGNORE_DUPS" to get the 
> zsh equivalent.  But if history ignores dups, then this ...
> 
> > setopt HIST_EXPIRE_DUPS_FIRST
> 
> ... is a no-op, because there won't be any dups to expire.

You're thinking of HIST_IGNORE_ALL_DUPS.  Setting HIST_IGNORE_DUPS just
tells zsh to ignore adjacent duplicates.

..wayne..

Re: Newbie zsh setup warts (history, pipes, export, ...).

[Oliver Kiddle]

Clint Adams wrote:
> > "set | less" works.  What's wrong with the grep?
> 
> grep is probably seeing the NUL character in IFS, and assuming.
> that the input is "binary".  Since you're using GNU grep, you can
> specify "grep -a" to override this assumption.

Alternatively, specify `typeset -H IFS' in your .zshrc to hide IFS in
the output of set.

Oliver

Re: Newbie zsh setup warts (history, pipes, export, ...).

[s. keeling]

Incoming from Wayne Davison:
> On Sun, Oct 24, 2004 at 06:11:16PM -0700, Bart Schaefer wrote:
> > You need "setopt HIST_IGNORE_DUPS" to get the 
> > zsh equivalent.  But if history ignores dups, then this ...
> 
> You're thinking of HIST_IGNORE_ALL_DUPS.  Setting HIST_IGNORE_DUPS just

Thanks to you all for the help.  It's remarkable how painless the
transition has been so far; everything just works.  I expected a lot
more gotchas in the process of swapping out something as fundamental
as a login shell.  Kudos to the developers.  :-)

Now, I'm hoping to sort out the difference in backgrounded jobs.
Specifically I can't say "sync & exit" anymore, or "startx & exit"
either.  Is this what "&!" is for?  I tried "nohup startx & exit"
yesterday and that seemed to just instantly kill the startx process.

I also need a little administrative help; are there any procmail users
on the list, and what do you use to tame zsh-users?  Here's what I've
come up with so far:

   # zsh-users
   #
   :0
   * 1^0 ^TO_zsh\-users
   * 1^0 ^Delivered\-To:.*zsh\-users
   * 1^0 ^Newsgroups:.*comp\.shells\.zsh
   {
     LOG="zsh-users - "
     :0:
     IN.zsh-users
   }


-- 
Any technology distinguishable from magic is insufficiently advanced.
(*)    http://www.spots.ab.ca/~keeling      Please don't Cc: me.
- -

Re: Newbie zsh setup warts (history, pipes, export, ...).

[Juhapekka Tolvanen]

"s. keeling" <keeling@spots.ab.ca> writes:

> I also need a little administrative help; are there any procmail users
> on the list, and what do you use to tame zsh-users? Here's what I've
> come up with so far:

>    # zsh-users
>    #
>    :0
>    * 1^0 ^TO_zsh\-users
>    * 1^0 ^Delivered\-To:.*zsh\-users
>    * 1^0 ^Newsgroups:.*comp\.shells\.zsh
>    {
>      LOG="zsh-users - "
>      :0:
>      IN.zsh-users
>    }


MAILSAVE=${HOME}/Maildir.mail/

THISMONTH="`date +%Y-%m`"

:0
* ^Mailing-List:.*zsh-users-help@sunsite\.dk.*
${MAILSAVE}zsh-users-${THISMONTH}/

Note!: Slash in the end of mailfolder-name means it is Maildir-formatted
folder, not boring old mbox-formatted folder.


-- 
Juhapekka "naula" Tolvanen * * http colon slash slash iki dot fi slash juhtolv
"kummaan paikkaan itsesi karkotit, syyttä syyllisten seuduille. raskaisiin
taloihin pesit, kirkuviin huoneisiin. mitä ne sinulle tekevät siellä? kuka on
raapinut nimesi pois, nimesi, kasvosi, mielesi oivat palvelemaan konetta?" CMX

Re: Newbie zsh setup warts (history, pipes, export, ...).

[Jason Price]

> Now, I'm hoping to sort out the difference in backgrounded jobs.
> Specifically I can't say "sync & exit" anymore, or "startx & exit"
> either.  Is this what "&!" is for?  I tried "nohup startx & exit"
> yesterday and that seemed to just instantly kill the startx process.

&! stands for (roughly) 'background and disown'.  You've always been able
to background jobs.  And if you started them correctly (aka with nohup) you
could log out, and the job wouldn't care (the 'hup' signal handler was
set).

zsh still allows nohup, but there's also a 'disown' builtin.  You can
disown a job, and it won't die when you log out either.  You can do this
post run time with 'disown %3' or the like (where %3 is the job number
gleaned from 'jobs').

The way to do this at runtime is to say 'your command and args &!'.

So, theoretically, 'startx &! ; exit' will work if you don't mind loosing
the short circuit.  Though I havn't needed to run startx in years...

### PROCMAIL STUFF

This works fairly well for me:

:0
* (^TO_|^Sender:[ 	]+owner-)zsh
zsh-list.spool

:0
* ^From:.*schaefer@brasslantern.com
* ^From:.*pws@csr.com
zsh-list.spool

I have no idea what PWS or Bart are/were doing with their mail to break
that procmail recipe, but once I did the hack below, the problem went away.

--Jason

Re: Newbie zsh setup warts (history, pipes, export, ...).

[s. keeling]

Incoming from Jason Price:
> 
> So, theoretically, 'startx &! ; exit' will work if you don't mind loosing

Works great.

> the short circuit.  Though I havn't needed to run startx in years...

I can't see the point of wasting RAM on [XKGW]DM.  With startx & exit,
I don't leave a logged in console lying around.

> ### PROCMAIL STUFF
> 
> This works fairly well for me:

Here's what I'm using now:

  :0
  * 1^0 ^(TO_|Sender:[ 	]+owner-)zsh
  * 1^0 ^From:.*(schaefer@brasslantern\.com\
     |duvall@comfychair\.org\
     |pws@csr\.com\
  )
  * 1^0 ^(Delivered\-To|Mailing\-List|Received):.*zsh\-
  * 1^0 ^Newsgroups:.*comp\.shells\.zsh
  * 1^0 ^Posted\-To:.*zsh
  {
    LOG="zsh-users - "
    :0:
    IN.zsh-users
  }

Thanks.


-- 
Any technology distinguishable from magic is insufficiently advanced.
(*)    http://www.spots.ab.ca/~keeling      Please don't Cc: me.
- -

Re: [ION Info #SZW-77636-264]: Re: Newbie zsh setup warts (history, pipes, export, ...).

[s. keeling]

Why is this happening?  I've been getting these on every post I make
to zsh-users.


Incoming from info@ionhosting.com:
> Hello,
> 
> Your request has been received and assigned ticket number SZW-77636-264. Depending on the complexity of your problem, your request is usually answered the same business day.
> 
> You can track your ticket at http://support.ionhosting.com. If you are not registered, you'll must with the same email address you used to send this inquiry.
> 
> Please review our Hosting FAQ at http://www.ionhosting.com/index.php?mode=service.hostingfaq and Resources section at http://www.ionhosting.com/index.php?mode=service.resources for answers to some common questions about all aspects of your account.
> 
> Best regards,
> 
> Help Desk
> ION Hosting
> info@ionhosting.com
> 

-- 
Any technology distinguishable from magic is insufficiently advanced.
(*)               http://www.spots.ab.ca/~keeling 
- -

Re: Newbie zsh setup warts (history, pipes, export, ...).

[Olivier Tharan]

On Mon, 25 Oct 2004 21:57:58 -0600, s. keeling <keeling@spots.ab.ca> wrote:
> I can't see the point of wasting RAM on [XKGW]DM.  With startx & exit,
> I don't leave a logged in console lying around.

Not strictly zsh-related, but you can use 'exec startx' which will
replace your running copy of the shell with startx, and therefore log
you out.

-- 
olive

Re: Newbie zsh setup warts (history, pipes, export, ...).

[Nikolai Weibull]

* s. keeling <keeling@spots.ab.ca> [Oct 26, 2004 12:56]:
> Here's what I'm using now:
>
>   :0
>   * 1^0 ^(TO_|Sender:[ 	]+owner-)zsh
>   * 1^0 ^From:.*(schaefer@brasslantern\.com\
>      |duvall@comfychair\.org\
>      |pws@csr\.com\
>   )
>   * 1^0 ^(Delivered\-To|Mailing\-List|Received):.*zsh\-
>   * 1^0 ^Newsgroups:.*comp\.shells\.zsh
>   * 1^0 ^Posted\-To:.*zsh
>   {
>     LOG="zsh-users - "
>     :0:
>     IN.zsh-users
>   }
>

What are the 1^0 supposed to do?
	nikolai

--
::: name: Nikolai Weibull    :: aliases: pcp / lone-star / aka :::
::: born: Chicago, IL USA    :: loc atm: Gothenburg, Sweden    :::
::: page: www.pcppopper.org  :: fun atm: gf,lps,ruby,lisp,war3 :::
main(){printf(&linux["\021%six\012\0"],(linux)["have"]+"fun"-97);}

Re: Newbie zsh setup warts (history, pipes, export, ...).

[s. keeling]

Incoming from Nikolai Weibull:
> * s. keeling <keeling@spots.ab.ca> [Oct 26, 2004 12:56]:
> > Here's what I'm using now:
> >
> >   :0
> >   * 1^0 ^(TO_|Sender:[ 	]+owner-)zsh
> >   * 1^0 ^From:.*(schaefer@brasslantern\.com\
> >      |duvall@comfychair\.org\
> >      |pws@csr\.com\
> >   )
> >   * 1^0 ^(Delivered\-To|Mailing\-List|Received):.*zsh\-
> >   * 1^0 ^Newsgroups:.*comp\.shells\.zsh
> >   * 1^0 ^Posted\-To:.*zsh
> >   {
> >     LOG="zsh-users - "
> >     :0:
> >     IN.zsh-users
> >   }
> >
> 
> What are the 1^0 supposed to do?

That's "scoring" (man procmailsc).  It's how you build OR rules in
procmail.  If _any_ of those conditions match, it's a match.  Without
scoring, all of those would have to match (AND) for it to be a match.

All procmail recipes start with a beginning score of -1.  Any of those
matching would add 1 to the score, thereby triggering the action
clause.


-- 
Any technology distinguishable from magic is insufficiently advanced.
(*)    http://www.spots.ab.ca/~keeling      Please don't Cc: me.
- -

Re: Newbie zsh setup warts (history, pipes, export, ...).

[Nikolai Weibull]

* s. keeling <keeling@spots.ab.ca> [Oct 26, 2004 17:20]:
> > > Here's what I'm using now:
> > >
> > >   :0
> > >   * 1^0 ^(TO_|Sender:[ 	]+owner-)zsh
> > >   * 1^0 ^From:.*(schaefer@brasslantern\.com\
> > >      |duvall@comfychair\.org\
> > >      |pws@csr\.com\
> > >   )
> > >   * 1^0 ^(Delivered\-To|Mailing\-List|Received):.*zsh\-
> > >   * 1^0 ^Newsgroups:.*comp\.shells\.zsh
> > >   * 1^0 ^Posted\-To:.*zsh
> > >   {
> > >     LOG="zsh-users - "
> > >     :0:
> > >     IN.zsh-users
> > >   }
> > >
> >
> > What are the 1^0 supposed to do?

> That's "scoring" (man procmailsc).

That was my guess.

> It's how you build OR rules in procmail.

Again, my guess, but definitely a weird way of having to do it.  Thanks
for showing this, I can use this in a few places myself.

> If _any_ of those conditions match, it's a match.  Without scoring,
> all of those would have to match (AND) for it to be a match.

Yes.  It's sad that there isn't an easier way to do it.

> All procmail recipes start with a beginning score of -1.  Any of those
> matching would add 1 to the score, thereby triggering the action
> clause.

Aha, OK.
	nikolai

--
::: name: Nikolai Weibull    :: aliases: pcp / lone-star / aka :::
::: born: Chicago, IL USA    :: loc atm: Gothenburg, Sweden    :::
::: page: www.pcppopper.org  :: fun atm: gf,lps,ruby,lisp,war3 :::
main(){printf(&linux["\021%six\012\0"],(linux)["have"]+"fun"-97);}

Re: Newbie zsh setup warts (history, pipes, export, ...).

[Bart Schaefer]

I suggest that further procmail discussion be re-routed to the procmail
list <procmail@lists.RWTH-Aachen.DE>.

On Mon, 25 Oct 2004, Jason Price wrote:

> ### PROCMAIL STUFF
> 
> This works fairly well for me:
> 
> :0
> * (^TO_|^Sender:[ 	]+owner-)zsh
> zsh-list.spool

I think you may want ^TO rather than ^TO_ there.  ^TO_ is for matching an
address, not a word.  Also, the zsh lists have not set a Sender: header
for a very long time; rather, they have

Delivered-To: mailing list zsh-user@sunsite.dk

(or zsh-workers, as appropriate).

> I have no idea what PWS or Bart are/were doing with their mail to break 
> that procmail recipe

Probably, sending you a personal copy, like I did with this message.

On Mon, 25 Oct 2004, s. keeling wrote:
> 
> Here's what I'm using now:
> 
>   :0
>   * 1^0 ^(TO_|Sender:[ 	]+owner-)zsh

This is broken, or at least useless.  The magic tokens are ^TO_ or ^TO 
(all the characters have to be consecutive).  You can't use TO_ or TO just 
anywhere.

On Tue, 26 Oct 2004, Nikolai Weibull wrote:

> > > What are the 1^0 supposed to do?
> 
> > That's "scoring" (man procmailsc).
> > It's how you build OR rules in procmail.
> 
> Again, my guess, but definitely a weird way of having to do it.

You don't HAVE to do it that way.  This works, too:

  :0
  * (^TO_|^Sender:[  ]+owner-)zsh\
   |^From:.*(schaefer@brasslantern\.com\
            |duvall@comfychair\.org\
            |pws@csr\.com\
            )\
   |^(Delivered\-To|Mailing\-List|Received):.*zsh\-\
   |^Newsgroups:.*comp\.shells\.zsh\
   |^Posted\-To:.*zsh

Just don't forget the backslashes at the ends of lines (and they must not 
have any spaces following them, before the newline).

> > All procmail recipes start with a beginning score of -1.

No, they start with a score of zero.  Only rules that accumulate a score
greater than zero trigger an action.

Re: Newbie zsh setup warts (history, pipes, export, ...).

[Nikolai Weibull]

* Bart Schaefer <schaefer@brasslantern.com> [Oct 26, 2004 18:30]:
> > I have no idea what PWS or Bart are/were doing with their mail to
> > break that procmail recipe

> Probably, sending you a personal copy, like I did with this message.

Yes, but the problem with doing that instead on only posting to the
mailing-list is that my mail provider only delivers one of them (rejects
dupes).  This is certainly annoying, as the only message I get winds up
in my INBOX.  Anyway, these discussions usually don't lead anyway, but
that's the main reason I don't like to be in a Cc:.

> > > > What are the 1^0 supposed to do?

> > > That's "scoring" (man procmailsc).
> > > It's how you build OR rules in procmail.

> > Again, my guess, but definitely a weird way of having to do it.

> You don't HAVE to do it that way.  This works, too:

>   :0
>   * (^TO_|^Sender:[  ]+owner-)zsh\
>    |^From:.*(schaefer@brasslantern\.com\
>             |duvall@comfychair\.org\
>             |pws@csr\.com\
>             )\
>    |^(Delivered\-To|Mailing\-List|Received):.*zsh\-\
>    |^Newsgroups:.*comp\.shells\.zsh\
>    |^Posted\-To:.*zsh

> Just don't forget the backslashes at the ends of lines (and they must not
> have any spaces following them, before the newline).

(Sorry for including this but...)  Yeah, but that's rather ugly.
	nikolai

--
::: name: Nikolai Weibull    :: aliases: pcp / lone-star / aka :::
::: born: Chicago, IL USA    :: loc atm: Gothenburg, Sweden    :::
::: page: www.pcppopper.org  :: fun atm: gf,lps,ruby,lisp,war3 :::
main(){printf(&linux["\021%six\012\0"],(linux)["have"]+"fun"-97);}

Re: Newbie zsh setup warts (history, pipes, export, ...).

[s. keeling]

Incoming from Bart Schaefer:
> I suggest that further procmail discussion be re-routed to the procmail
> list <procmail@lists.RWTH-Aachen.DE>.

Agreed.

> On Mon, 25 Oct 2004, s. keeling wrote:
> > 
> >   * 1^0 ^(TO_|Sender:[ 	]+owner-)zsh
> 
> This is broken, or at least useless.  The magic tokens are ^TO_ or ^TO 
> [snip]
> > > All procmail recipes start with a beginning score of -1.
> [snip]
> No, they start with a score of zero.  Only rules that accumulate a score
> greater than zero trigger an action.

Thanks for the corrections.  I should have known those by now.


-- 
Any technology distinguishable from magic is insufficiently advanced.
(*)    http://www.spots.ab.ca/~keeling      Please don't Cc: me.
- -