unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Juri Linkov <juri@jurta.org>
To: Warren Harris <warrensomebody@gmail.com>
Cc: 5976@debbugs.gnu.org
Subject: bug#5976: 23.1.93; yanking shell commands - converted to single lines
Date: Wed, 21 Apr 2010 11:43:36 +0300	[thread overview]
Message-ID: <87bpddgrl3.fsf@mail.jurta.org> (raw)
In-Reply-To: <F9C653DA-9D59-49A5-B9F9-F8CAC67E042A@gmail.com> (Warren Harris's message of "Tue, 20 Apr 2010 09:29:08 -0700")

>> Doing this in bash, I get the same result because it saves multi-line
>> commands on separate lines in ~/.bash_history and reads each line as
>> a separate command.  Why should Emacs be different in this regard?
>
> I could have sworn that aquamacs 1.9 preserved multi-line shell commands
> across shell sessions, but perhaps I'm mistaken. It certainly  does
> preserve multi-line shell commands within a single shell session.

Bash preserves multi-line shell commands within a single shell session too
when its shopt option `cmdhist' is set.

There is also the option `lithist' that replaces newlines with semicolon
separators.  But it doesn't help because it doesn't replace newlines
inside command line arguments.

So I see no way to save multi-line shell commands in ~/.bash_history
in a way compatible with Bash.  Do you have any ideas?

-- 
Juri Linkov
http://www.jurta.org/emacs/






  reply	other threads:[~2010-04-21  8:43 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-04-19 19:28 bug#5976: 23.1.93; yanking shell commands - converted to single lines David Reitter
2010-04-19 22:54 ` Juri Linkov
2010-04-20 16:29   ` Warren Harris
2010-04-21  8:43     ` Juri Linkov [this message]
2010-04-21 10:13       ` Thierry Volpiatto
2010-04-21 15:41         ` Juri Linkov
2010-04-21 17:36           ` Thierry Volpiatto
2016-06-08  3:13 ` Noam Postavsky

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=87bpddgrl3.fsf@mail.jurta.org \
    --to=juri@jurta.org \
    --cc=5976@debbugs.gnu.org \
    --cc=warrensomebody@gmail.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).