zsh-workers
 help / color / mirror / code / Atom feed
From: Emanuel Berg <embe8573@student.uu.se>
To: zsh-workers@zsh.org
Subject: Re: implicit previous command, only state what should change
Date: Wed, 16 Jul 2014 22:45:35 +0200	[thread overview]
Message-ID: <87r41ldocw.fsf@debian.uxu> (raw)
In-Reply-To: <20140716145433.073fda81@pwslap01u.europe.root.pri> (Peter Stephenson's message of "Wed, 16 Jul 2014 14:54:33 +0100")

Peter Stephenson <p.stephenson@samsung.com> writes:

> The bit you quote is a reference to the details of
> the patch, which you can ignore unless you're
> particularly interested in the implementation.
>
> What I should have said but didn't was, here's a new
> function called replace-argument that does that.
> That was in the body of the patch, but unless you're
> programmed to look at zsh code patches when a new
> message arrives you wouldn't notice.

Aha, yes, now I see it. I have configured Gnus to
auto-fill messages, which works great for text, but
scrambles code, so I didn't see it (it looks like a PGP
key or something).

Are you suggesting I apply it to the zsh source and
recompile?

If so, how do I use it after that (i.e., what
notation)?

When I upgrade zsh, wont it disappear?

> I'll commit it when I have a couple of minutes spare.

You mean to the official zsh source or do you have your
own branch?

/The hairdresser

-- 
underground experts united


  reply	other threads:[~2014-07-16 20:45 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-13 22:06 Emanuel Berg
2014-07-13 22:24 ` Frank Terbeck
2014-07-13 22:50   ` Emanuel Berg
2014-07-14  2:08     ` Mikael Magnusson
2014-07-14 13:09       ` Emanuel Berg
2014-07-15  6:46 ` Bart Schaefer
2014-07-15 15:42   ` Emanuel Berg
2014-07-15 16:58 ` Peter Stephenson
2014-07-16  0:36   ` Emanuel Berg
2014-07-16 13:54     ` Peter Stephenson
2014-07-16 20:45       ` Emanuel Berg [this message]
2014-07-16 20:53         ` Bart Schaefer
2014-07-16 21:08           ` Emanuel Berg
2014-07-17  8:17         ` Peter Stephenson
2014-07-17 13:01           ` Emanuel Berg

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=87r41ldocw.fsf@debian.uxu \
    --to=embe8573@student.uu.se \
    --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).