From: Aidan Gauland <aidalgol@no8wireless.co.nz>
To: emacs-devel@gnu.org
Subject: Re: [Eshell patch] Visual subcommands and options
Date: Mon, 03 Jun 2013 12:11:26 +1200 [thread overview]
Message-ID: <874ndg3vf5.fsf@dimension8.tehua.net> (raw)
In-Reply-To: 87k3mcamkm.fsf@thinkpad.tsdh.de
Tassilo Horn <tsdh@gnu.org> writes:
> If the output is large as with "git/bzr log", you have wait until it's
> all there before starting to, say, search. And since the most recent
> commits are on top of the output, I prefer starting there than below the
> initial commit.
Oh yeah, good point. I should see if there's some other way that's
non-blocking. Maybe there's a value for PAGER that tells the programs
to just dump to stdout.
> Well, but your approach has the benefit that you can use standard emacs
> commands whereas I have to fiddle with what the pager provides. Hm, is
> there something that lets me do isearch in a term buffer and gives me a
> point so that I can copy and yank? Currently, I'm mousing my way
> there...
You can use C-c C-j to switch to normal Emacs line-oriented mode (called
term-line-mode, which is not actually a mode), and C-c C-k to switch
back to terminal mode. You still have to use the pager to scroll and
search, though.
> Great, thanks. Installed as revno 112822.
Thanks for the contribution!
--Aidan
next prev parent reply other threads:[~2013-06-03 0:11 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-31 10:58 [Eshell patch] Visual subcommands and options Tassilo Horn
2013-06-01 9:49 ` Tassilo Horn
2013-06-01 21:41 ` Aidan Gauland
2013-06-02 9:28 ` Tassilo Horn
2013-06-03 0:11 ` Aidan Gauland [this message]
2013-06-03 7:15 ` Tassilo Horn
2013-06-03 20:04 ` Aidan Gauland
[not found] ` <87hahel63t.fsf_-_@thinkpad.tsdh.de>
2013-06-07 3:56 ` Some more eshell problems Aidan Gauland
2013-06-07 11:38 ` Tassilo Horn
2013-06-07 12:39 ` Thierry Volpiatto
2013-06-07 16:25 ` Tassilo Horn
2013-06-09 7:07 ` Eshell visual commands with redirection bug Aidan Gauland
2013-06-09 9:47 ` Tassilo Horn
2013-06-10 1:41 ` Aidan Gauland
2013-06-10 7:21 ` Tassilo Horn
2013-06-10 8:20 ` Aidan Gauland
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=874ndg3vf5.fsf@dimension8.tehua.net \
--to=aidalgol@no8wireless.co.nz \
--cc=emacs-devel@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).