From: Nick Roberts <nickrob@gnu.org>
Subject: [PATCH] Emacs manual
Date: Thu, 17 Jun 2004 22:03:47 +0100 [thread overview]
Message-ID: <16594.1843.339547.195781@nick.uklinux.net> (raw)
How about the following patch for misc.texi?
It does the following:
1) Moves comint-dynamic-list-input-ring to the Shell History Ring section.
2) Indexes comint-input-previous-argument and comint-get-next-from-history
properly.
3) Documents comint-insert-clicked-input.
Nick
*** misc.texi.~1.50.~ 2004-03-24 20:26:30.000000000 +0000
--- misc.texi 2004-06-17 21:54:17.000000000 +0100
***************
*** 624,635 ****
Move backward across one shell command, but not beyond the current line
(@code{shell-backward-command}).
- @item C-c C-l
- @kindex C-c C-l @r{(Shell mode)}
- @findex comint-dynamic-list-input-ring
- Display the buffer's history of shell commands in another window
- (@code{comint-dynamic-list-input-ring}).
-
@item M-x dirs
Ask the shell what its current directory is, so that Emacs can agree
with the shell.
--- 624,629 ----
***************
*** 740,752 ****
@itemx M-s @var{regexp} @key{RET}
Search backwards or forwards for old shell commands that match @var{regexp}.
! @item C-c C-x @r{(Shell mode)}
@findex comint-get-next-from-history
Fetch the next subsequent command from the history.
! @item C-c . @r{(Shell mode)}
@findex comint-input-previous-argument
Fetch one argument from an old shell command.
@end table
Shell buffers provide a history of previously entered shell commands. To
--- 734,754 ----
@itemx M-s @var{regexp} @key{RET}
Search backwards or forwards for old shell commands that match @var{regexp}.
! @item C-c C-x
! @kindex C-c C-x @r{(Shell mode)}
@findex comint-get-next-from-history
Fetch the next subsequent command from the history.
! @item C-c .
! @kindex C-c . @r{(Shell mode)}
@findex comint-input-previous-argument
Fetch one argument from an old shell command.
+
+ @item C-c C-l
+ @kindex C-c C-l @r{(Shell mode)}
+ @findex comint-dynamic-list-input-ring
+ Display the buffer's history of shell commands in another window
+ (@code{comint-dynamic-list-input-ring}).
@end table
Shell buffers provide a history of previously entered shell commands. To
***************
*** 822,827 ****
--- 824,837 ----
move point back to a previous command. After you copy the command, you
can submit the copy as input with @key{RET}. If you wish, you can
edit the copy before resubmitting it.
+
+ @kindex Mouse-2 @r{(Shell mode)}
+ @findex comint-insert-clicked-input
+ @item Mouse-2
+ Select the input command that you click on to be current input
+ (@code{comint-insert-clicked-input}). Like
+ @code{comint-copy-old-input} but further clicks replace the current
+ input instead of adding to it.
@end table
Moving to a previous input and then copying it with @kbd{C-c
reply other threads:[~2004-06-17 21:03 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=16594.1843.339547.195781@nick.uklinux.net \
--to=nickrob@gnu.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).