zsh-workers
 help / color / mirror / code / Atom feed
From: Bart Schaefer <schaefer@brasslantern.com>
To: zsh-workers@zsh.org
Subject: Re: Regarding emulate: a thought, and refresh my memory?
Date: Tue, 06 Mar 2012 22:38:06 -0800	[thread overview]
Message-ID: <120306223806.ZM11578@torch.brasslantern.com> (raw)
In-Reply-To: <20120306202201.GD4383@yahoo.fr>

On Mar 6,  8:22pm, Stephane Chazelas wrote:
} Subject: Re: Regarding emulate: a thought, and refresh my memory?
}
} 2012-03-06 20:06:52 +0000, Peter Stephenson:
} [...]
} > Can't see why not.  I often do "emulate -L zsh; setopt extendedglob
} > cbases", it would be sensible to put that in one command.
} [...]
} 
} What about special parameters like:
} 
} zsh_options=(noshwordsplit noposixstrings...)
} 
} emulate -L $zsh_options extendedglob

Yes, that's the idea, just not the precise formulation.

The first word (that doesn't begin with a hyphen) seen by "emulate" has
to be the name of the emulation mode.  So, based on PWS's feedback I've
just committed 30320, which enables for example this:

    zsh_options=(noshwordsplit noposixstrings ...)

    emulate -L zsh --$^zsh_options --extendedglob

Hmm, I should probably add a bit of doc to the description of the -c
flag pointing out that only the emulation mode is sticky, not the full
set of options one might throw in.

Unless PWS, who knows more about how the sticky emulation works than
I do, has a clever idea about that?


  reply	other threads:[~2012-03-07  6:38 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-04  1:25 Bart Schaefer
2012-03-06  8:27 ` PATCH " Bart Schaefer
2012-03-06 20:06 ` Peter Stephenson
2012-03-06 20:22   ` Stephane Chazelas
2012-03-07  6:38     ` Bart Schaefer [this message]
2012-03-07 11:34       ` Stephane Chazelas
2012-03-07 17:45         ` Bart Schaefer
2012-03-08  8:38           ` Stephane Chazelas
2012-03-08 15:08             ` 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=120306223806.ZM11578@torch.brasslantern.com \
    --to=schaefer@brasslantern.com \
    --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).