unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Sebastien Vauban <sva-news-D0wtAvR13HarG/iDocfnWg@public.gmane.org>
To: 16012-ubl+/3LiMTaZdePnXv/OxA@public.gmane.org
Subject: bug#16012: Multi-line shell commands appear as one-liners in the history
Date: Mon, 25 Aug 2014 20:45:52 +0200	[thread overview]
Message-ID: <861ts4qufz.fsf@somewhere.org> (raw)
In-Reply-To: <86eh5yb4ls.fsf-oHC15RC7JGTNLxjTenLetw@public.gmane.org>

Hello,

>> ls \
>> *.html
>>
>> Recalling the previous command will just show "*.html", not "ls
>>\\n*.html".
>
> Right, currently shell-mode has no idea that these were two lines of
> the same command.  The semantics of a terminating backslash completely
> eludes it.
>
>> Is there a solution to this?
>
> A patch for shell.el would probably do it, assuming it's the right
> patch ;-)

I've just read notes about "Comint Patch":

  ╭────
  │ If you enter a multi-line SQL statement in an SQLi buffer, you can
  │ retrieve it as a multi-line command from the MinibufferHistory. Not so
  │ when you exit Emacs and restart it at a later date: As you exit SQLi
  │ mode the command history is written to a file; when you enter SQLi mode
  │ again the history is loaded one command per line. If you entered
  │ multi-line commands, each line of those commands will end up as one
  │ command in the input history of your new session.
  │ 
  │ This patch will be in Emacs 21.
  ╰────

See http://www.emacswiki.org/emacs-es/ComintPatched

Aren't we talking of this bug?  If yes, why isn't it yet in Emacs, then?

Best regards,
  Seb

-- 
Sebastien Vauban





  parent reply	other threads:[~2014-08-25 18:45 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-30  9:50 bug#16012: 24.3.50; Multi-line shell commands appear as one-liners in the history Sebastien Vauban
2013-12-01 21:13 ` Stefan Monnier
     [not found] ` <86eh5yb4ls.fsf-oHC15RC7JGTNLxjTenLetw@public.gmane.org>
2014-08-25 18:45   ` Sebastien Vauban [this message]
2021-07-15  5:22     ` Lars Ingebrigtsen

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=861ts4qufz.fsf@somewhere.org \
    --to=sva-news-d0wtavr13harg/idocfnwg@public.gmane.org \
    --cc=16012-ubl+/3LiMTaZdePnXv/OxA@public.gmane.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.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).