all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Juri Linkov <juri@linkov.net>
To: Kevin Ryde <user42_kevin@yahoo.com.au>
Cc: 19812@debbugs.gnu.org
Subject: bug#19812: 24.4; suggest `shell-mode' not interactive
Date: Tue, 06 Aug 2019 00:59:45 +0300	[thread overview]
Message-ID: <87v9vbtgry.fsf@mail.linkov.net> (raw)
In-Reply-To: <87d0hk2drc.fsf@blah.blah> (Kevin Ryde's message of "Mon, 05 Aug 2019 18:54:47 +1000")

>> It might be useful to visit log files previously saved from shell buffers,
>> like compilation-mode adds such local-variable prop-line:
>>
>>   -*- mode: compilation -*-
>
> I suppose the difference is compilation-mode does useful things when a
> compilation has finished, whereas shell-mode and similar would be more
> or less entirely for interaction.

It makes sense to visit a previously saved shell buffer only to
see highlighted prompts and command lines (that shell-mode
currently is unable to do).

> I've had file buffers in compilation-mode for stepping error lines in
> the way you say.  The only thing I've been tricked by is accidentally
> "g" recompile which replaces the file text -- in a sensible way, but for
> me usually not what I meant to do :-).

Maybe "g" should check if the compilation buffer is visiting a file,
and not to recompile in this case.





  reply	other threads:[~2019-08-05 21:59 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-08  4:07 bug#19812: 24.4; suggest `shell-mode' not interactive Kevin Ryde
2019-08-02 19:52 ` Lars Ingebrigtsen
2019-08-02 23:54   ` Kevin Ryde
2019-08-03 11:11     ` Lars Ingebrigtsen
2019-08-03  7:22   ` Eli Zaretskii
2019-08-03 11:08     ` Lars Ingebrigtsen
2019-08-04 19:11       ` Juri Linkov
2019-08-05  8:54         ` Kevin Ryde
2019-08-05 21:59           ` Juri Linkov [this message]
2019-08-07  6:46             ` Kevin Ryde
2019-08-23  0:59     ` Lars Ingebrigtsen
2019-08-27 22:13       ` Juri Linkov

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=87v9vbtgry.fsf@mail.linkov.net \
    --to=juri@linkov.net \
    --cc=19812@debbugs.gnu.org \
    --cc=user42_kevin@yahoo.com.au \
    /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 external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.