From: Chris <chrisl_ak@hotmail.com>
Subject: RE: alternatives to dired
Date: Sat, 05 Oct 2002 03:16:27 -0000 [thread overview]
Message-ID: <Xns929DC3F22222Dchrislak@216.168.3.40> (raw)
In-Reply-To: mailman.1033740246.31504.help-gnu-emacs@gnu.org
on 04 Oct 2002, ken <ken@cleveland.lug.net> spake thusly:
>
> When in emacs I do "C-h f dired", emacs says:
>
> dired is an interactive autoloaded Lisp function in `dired'.
>
> "Edit" directory DIRNAME--delete, rename, print, etc. some files in it.
> Optional second argument SWITCHES specifies the `ls' options used.
> (Interactively, use a prefix argument to be able to specify SWITCHES.)
You can also set the switches for a long and short (gotten to by C-x C-d)
listing. The problem is, unless there is a -l switch present, dired doesn't
function.
next parent reply other threads:[~2002-10-05 3:16 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.1033740246.31504.help-gnu-emacs@gnu.org>
2002-10-05 3:16 ` Chris [this message]
2002-10-04 9:08 alternatives to dired Victor Kirk
2002-10-04 14:03 ` ken
-- strict thread matches above, loose matches on Subject: below --
2002-10-03 4:07 ftrw
2002-10-03 5:04 ` Edward O'Connor
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=Xns929DC3F22222Dchrislak@216.168.3.40 \
--to=chrisl_ak@hotmail.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.
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).