From: Nick Roberts <nickrob@snap.net.nz>
Cc: rogers-emacs@rgrjr.dyndns.org, emacs-devel@gnu.org
Subject: Re: comint-insert-input on non-command lines:
Date: Thu, 11 May 2006 09:38:29 +1200 [thread overview]
Message-ID: <17506.23893.746029.146542@farnswood.snap.net.nz> (raw)
In-Reply-To: <200605100606.k4A661Rs019271@jane.dms.auburn.edu>
> I claimed that the mouse-2 behavior was confusing with your latest
> changes applied and with comint-use-prompt-regexp non-nil. How long
> have you been using mouse-2 in this situation? mouse-2 copies old
> text to the current command line in the entire Comint buffer and never
> yanks. This is very confusing behavior to me.
The first complaint was that C-c RET doesn't work everywhere, now you're
saying you don't like it because mouse-2 *does* work everyhere.
> Fields provide the opportunity to distinguish between input and output:
> I think we should use it.
>
> I was talking about people who wanted to use `C-c RET' to insert old
> output at the current prompt. Given the current code, people who want
> that have to set comint-use-prompt-regexp non-nil and hence can not
> use fields. That is what seems weird to me.
Thats how comint works: with comint-prompt-regexp or with fields. Its not my
choosing.
Anyway, my position seems to be increasingly untenable so I've put
comint-copy-old-input back on C-c RET and comint-insert-input just on mouse-2.
As you are more enthusiastic about this arrangement than me, could you please
update the docs. I don't intend to make any further changes to comint.el so
you are free to do so if you wish.
--
Nick http://www.inet.net.nz/~nickrob
next prev parent reply other threads:[~2006-05-10 21:38 UTC|newest]
Thread overview: 47+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-06 20:05 comint-insert-input on non-command lines: A trivial fix, a quibble, and a bug Bob Rogers
2006-05-08 0:31 ` Nick Roberts
2006-05-08 3:16 ` Luc Teirlinck
2006-05-08 3:49 ` Luc Teirlinck
2006-05-08 4:49 ` Miles Bader
2006-05-08 14:08 ` Stefan Monnier
2006-05-09 2:33 ` Miles Bader
2006-05-08 4:08 ` Luc Teirlinck
2006-05-08 4:18 ` Nick Roberts
2006-05-09 1:55 ` Bob Rogers
2006-05-09 3:11 ` Nick Roberts
2006-05-10 3:01 ` Bob Rogers
2006-05-10 5:57 ` Nick Roberts
2006-05-09 3:01 ` Luc Teirlinck
2006-05-09 3:21 ` Nick Roberts
2006-05-09 3:59 ` Luc Teirlinck
2006-05-09 6:17 ` Nick Roberts
2006-05-09 14:58 ` Luc Teirlinck
2006-05-10 1:09 ` Nick Roberts
2006-05-10 1:13 ` Luc Teirlinck
2006-05-10 1:58 ` Miles Bader
2006-05-10 2:21 ` Nick Roberts
2006-05-10 2:32 ` Miles Bader
2006-05-10 3:50 ` Nick Roberts
2006-05-10 4:09 ` Miles Bader
2006-05-10 4:41 ` Luc Teirlinck
2006-05-10 5:29 ` Nick Roberts
2006-05-10 6:06 ` Luc Teirlinck
2006-05-10 6:27 ` Miles Bader
2006-05-10 21:38 ` Nick Roberts [this message]
2006-05-11 1:12 ` comint-insert-input on non-command lines: Luc Teirlinck
2006-05-11 1:33 ` Luc Teirlinck
2006-05-11 18:31 ` Richard Stallman
2006-05-11 20:29 ` Nick Roberts
2006-05-11 22:40 ` Luc Teirlinck
2006-05-14 23:29 ` Richard Stallman
2006-05-15 3:46 ` Luc Teirlinck
2006-05-15 20:37 ` Richard Stallman
2006-05-28 2:11 ` Luc Teirlinck
2006-05-28 3:48 ` Luc Teirlinck
2006-05-29 3:41 ` Nick Roberts
2006-05-29 3:58 ` Luc Teirlinck
2006-05-31 3:14 ` Luc Teirlinck
2006-05-31 3:24 ` Bob Rogers
2006-05-09 4:15 ` comint-insert-input on non-command lines: A trivial fix, a quibble, and a bug Luc Teirlinck
2006-05-10 5:19 ` Luc Teirlinck
2006-05-10 6:04 ` Nick Roberts
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=17506.23893.746029.146542@farnswood.snap.net.nz \
--to=nickrob@snap.net.nz \
--cc=emacs-devel@gnu.org \
--cc=rogers-emacs@rgrjr.dyndns.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).