From: Bob Portmann <bportmann@yahoo.com>
Subject: Re: comint-accumulate-marker
Date: Sat, 15 Apr 2006 17:19:01 -0700 (PDT) [thread overview]
Message-ID: <20060416001901.83803.qmail@web60324.mail.yahoo.com> (raw)
In-Reply-To: <pan.2006.04.13.19.45.08.857173@as.arizona.edu>
--- JD Smith <jdsmith@as.arizona.edu> wrote:
> `comint-accumulate-marker' should (I believe) be left at the process
> mark when lines are accumulated. To see this:
>
> M-x shell
> echo this is test 1 [RET]
> echo this is test 2; [C-c SPC]
> echo this is more test 2 [M-p]
>
> The entire accumulated command should be replaced by the previous
> item
> on the input history, but it is not, since the accumulate marker was
> moved to the beginning of the 2nd line ("this is more test 2"), and
> use to
> mark the beginning of the region which is replaced by the historical
> command.
>
> I noticed this while I was implementing a comint feature in my
> IDLWAVE
> mode. It occurs to me that this feature might be a useful option for
> all comint modes, and might be better added there. In a terminal
> shell, using up arrow to recall history doesn't clobber the partially
> complete command you are composing. If you go back down, it is still
> there (even if it's blank).
I, for one, would welcome this change in shell (and other shell like)
modes. I MUCH prefer the way regular terms work where one can go up in
the history and then back down and still have a blank line (or whatever
was there). Going immediately to the opposite end of the ring is
disorienting when one has lots (1000+) of things saved in the history.
And then it is a pain to type C-x u to get a blank line again.
It also seems to go against the emacs philosophy that this behavior
cannot (easily) be configured.
Bob
> Not so in comint modes. Going down with
> M-p only wraps you around the input ring. You can emulate the
> terminal shell behavior by pretending there is another node on the
> ring between index 0 and the last ring index, and save the partially
> completed command when you stop "on" or "off" the ring. I'd envision
> this as a user option.
>
> Do we have a 22.1 pre-release branch where only bug-fixes are being
> applied, vs. HEAD where new features are being placed?
>
>
>
>
> _______________________________________________
> Emacs-devel mailing list
> Emacs-devel@gnu.org
> http://lists.gnu.org/mailman/listinfo/emacs-devel
>
__________________________________________________
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around
http://mail.yahoo.com
next prev parent reply other threads:[~2006-04-16 0:19 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-13 19:45 comint-accumulate-marker JD Smith
2006-04-16 0:19 ` Bob Portmann [this message]
2006-04-16 2:09 ` comint-accumulate-marker Richard Stallman
2006-04-17 18:06 ` comint-accumulate-marker JD Smith
2006-04-18 9:47 ` comint-accumulate-marker Nick Roberts
2006-04-18 11:25 ` comint-accumulate-marker Stefan Monnier
2006-04-18 20:50 ` comint-accumulate-marker Richard Stallman
2006-04-18 12:57 ` comint-accumulate-marker Richard Stallman
2006-04-18 19:10 ` comint-accumulate-marker JD Smith
2006-04-18 20:54 ` comint-accumulate-marker David Kastrup
2006-04-18 21:06 ` comint-accumulate-marker JD Smith
2006-04-18 23:25 ` comint-accumulate-marker Stuart D. Herring
2006-04-18 21:22 ` comint-accumulate-marker Nick Roberts
2006-04-18 21:38 ` comint-accumulate-marker JD Smith
2006-04-18 23:24 ` comint-accumulate-marker Nick Roberts
[not found] ` <1145403002.27500.42.camel@turtle.as.arizona.edu>
2006-04-19 0:01 ` comint-accumulate-marker Nick Roberts
2006-04-19 0:01 ` Bug in diff-mode? (was: Re: comint-accumulate-marker) Nick Roberts
2006-04-19 15:40 ` Richard Stallman
2006-04-19 15:40 ` comint-accumulate-marker Richard Stallman
2006-04-20 7:25 ` comint-accumulate-marker David Kastrup
2006-04-20 7:45 ` comint-accumulate-marker Nick Roberts
2006-04-20 17:29 ` comint-accumulate-marker JD Smith
2006-04-18 22:21 ` comint-accumulate-marker Stuart D. Herring
2006-04-18 22:48 ` comint-accumulate-marker JD Smith
2006-04-18 23:39 ` comint-accumulate-marker Miles Bader
2006-04-19 0:02 ` comint-accumulate-marker JD Smith
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=20060416001901.83803.qmail@web60324.mail.yahoo.com \
--to=bportmann@yahoo.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).