From: Tyler Smith <tyler.smith@mail.mcgill.ca>
To: help-gnu-emacs@gnu.org
Subject: Re: Quite a few emacs questions
Date: 18 May 2007 00:08:31 GMT [thread overview]
Message-ID: <slrnf4pv4h.3pc.tyler.smith@blackbart.mynetwork> (raw)
In-Reply-To: 1179438643.818287.167270@w5g2000hsg.googlegroups.com
On 2007-05-17, mowgli <knowledgeless@gmail.com> wrote:
>
> Well, I had alerady have done it before posting any questions here. I
> forgot that even in the shell I have to use these keys to just list
> the directory contents. It's a bit tedious though, don't you think,
> when on the actual console, we need not do such things?
>
I'm not sure what you mean - when you're running a straight console
how do you avoid having ls scroll off the screen? Other than piping it
into less, I don't know how you'd do it.
In emacs you have all kinds of ways to deal with long output. If you
don't like scrolling backwards through the output, you can type C-c
C-p, which will move you back to the last prompt, so you can scroll
forwards through the output. But if the output is longer than the
length of the screen you will have to scroll to see it all. Emacs
can't make 100 lines of output fit on a 40 line screen.
Something else you could try is C-x d, which will prompt you for the
directory you want to see. The contents of the directory are put into
a window that you can scroll up and down in, open, rename, delete,
move files, all kinds of stuff. There's a whole suite of commands
available from within this buffer, called dired-mode. You'll need to
read the manual to find out all the details.
HTH,
Tyler
next prev parent reply other threads:[~2007-05-18 0:08 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-16 0:42 Quite a few emacs questions mowgli
2007-05-16 7:05 ` Tassilo Horn
2007-05-17 0:23 ` mowgli
2007-05-17 9:22 ` Tassilo Horn
2007-05-17 12:03 ` David Kastrup
2007-05-19 21:21 ` Ian J Cottee
2007-05-17 9:30 ` Daniel Jensen
2007-05-16 21:07 ` Amy Templeton
2007-05-16 21:58 ` Peter Dyballa
2007-05-17 0:43 ` knowledge less
2007-05-17 8:42 ` Peter Dyballa
[not found] ` <mailman.751.1179353187.32220.help-gnu-emacs@gnu.org>
2007-05-17 7:01 ` mowgli
[not found] ` <mailman.749.1179349827.32220.help-gnu-emacs@gnu.org>
2007-05-17 19:33 ` mowgli
2007-05-17 19:53 ` Lowell Gilbert
2007-05-17 20:35 ` Tyler Smith
2007-05-17 21:50 ` mowgli
2007-05-18 0:08 ` Tyler Smith [this message]
2007-05-18 0:27 ` mowgli
2007-05-18 0:56 ` Tyler Smith
2007-05-18 7:18 ` Thien-Thi Nguyen
2007-05-18 8:26 ` mowgli
2007-05-18 19:34 ` Dieter Wilhelm
2007-05-22 4:38 ` Xavier Maillard
2007-05-18 0:33 ` mowgli
2007-05-19 11:46 ` mowgli
2007-05-19 12:56 ` Lennart Borgman (gmail)
[not found] ` <mailman.855.1179579415.32220.help-gnu-emacs@gnu.org>
2007-05-22 9:50 ` mowgli
2007-05-22 10:53 ` Lennart Borgman (gmail)
2007-05-22 21:45 ` Xavier Maillard
[not found] ` <mailman.969.1179831210.32220.help-gnu-emacs@gnu.org>
2007-05-23 0:58 ` mowgli
2007-05-23 9:26 ` Lennart Borgman (gmail)
2007-05-23 21:36 ` Allan Gottlieb
2007-05-23 21:40 ` Lennart Borgman (gmail)
2007-05-23 22:26 ` Allan Gottlieb
[not found] <mailman.1043.1179871359.32220.help-gnu-emacs@gnu.org>
2007-05-23 0:50 ` mowgli
2007-05-23 0:59 ` mowgli
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=slrnf4pv4h.3pc.tyler.smith@blackbart.mynetwork \
--to=tyler.smith@mail.mcgill.ca \
--cc=help-gnu-emacs@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.
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).