From: npostavs@users.sourceforge.net
To: George Plymale II <georgedp@orbitalimpact.com>
Cc: 26161@debbugs.gnu.org
Subject: bug#26161: 25.1; `eshell-exit-success-p' determines that Lisp commands are successful if they return non-nil
Date: Thu, 20 Apr 2017 23:10:52 -0400 [thread overview]
Message-ID: <87k26eqwub.fsf@users.sourceforge.net> (raw)
In-Reply-To: <m0zifadfoe.fsf@lehi.dev.orbitalimpact.com> (George Plymale, II's message of "Thu, 20 Apr 2017 15:47:45 -0400")
tags 26161 fixed
close 26161 26.1
quit
George Plymale II <georgedp@orbitalimpact.com> writes:
> Thanks for the advice. Apologies for the crappy formatting on my last
> message. I think my system mail client and my Emacs mail client had a
> disagreement and it ended up looking like that.
It looked a bit funny, but there was no line wrapping so it didn't do
any harm.
> So now I'm sending this
> directly via the Emacs mail client (hopefully it doesn't screw stuff up
> either). The requested patch is attached now to this message, so please
> let me know if you need anything else.
Thanks, pushed to master [1: e8875bcbe0]. I reformatted your commit
message to conform to the ChangeLog format and marked this as a
copyright exempt change.
1: 2017-04-20 23:03:10 -0400
Treat non-erroring lisp call as successful eshell command (Bug#26161)
http://git.savannah.gnu.org/cgit/emacs.git/commit/?id=e8875bcbe067ea020dba95530ec4e9485942babd
prev parent reply other threads:[~2017-04-21 3:10 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-18 19:12 bug#26161: 25.1; `eshell-exit-success-p' determines that Lisp commands are successful if they return non-nil George D. Plymale
2017-03-31 3:52 ` npostavs
2017-04-01 23:46 ` George D. Plymale
2017-04-02 0:06 ` npostavs
2017-04-11 19:48 ` George D. Plymale
2017-04-13 1:18 ` npostavs
2017-04-20 19:47 ` George Plymale II
2017-04-21 3:10 ` npostavs [this message]
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87k26eqwub.fsf@users.sourceforge.net \
--to=npostavs@users.sourceforge.net \
--cc=26161@debbugs.gnu.org \
--cc=georgedp@orbitalimpact.com \
/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.savannah.gnu.org/cgit/emacs.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).