From: arthur miller <arthur.miller@live.com>
To: Drew Adams <drew.adams@oracle.com>,
Marco Wahl <marcowahlsoft@gmail.com>,
"Basil L. Contovounesios" <contovob@tcd.ie>
Cc: "42578@debbugs.gnu.org" <42578@debbugs.gnu.org>
Subject: bug#42578: 28.0.50; [suggestion] allow dired-do-shell-command on directory line
Date: Wed, 29 Jul 2020 00:17:04 +0000 [thread overview]
Message-ID: <VI1PR06MB452635C56B337968DE8B6D2296700@VI1PR06MB4526.eurprd06.prod.outlook.com> (raw)
In-Reply-To: <87zh7kexk7.fsf@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 632 bytes --]
Skickat från min Samsung Galaxy-smartphone.
> I'm talking about those dired headlines here.
> Dired headlines are not file or directory lines.
> They're not acted on by ! or (most) other
> commands.
Unfortunately some commands, like go to start of buffer (or what is the name) put cursor on first line (header) in dired which is a bit annoying since it is useless. In dired it makes more sense to move cursor/point to start of the first line after the header (first file). I have bound a key to move it so and use that key instead of ordinary move to the beginning of a buffer (C-<home > by default I think).
[-- Attachment #2: Type: text/html, Size: 1297 bytes --]
next prev parent reply other threads:[~2020-07-29 0:17 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-28 10:36 bug#42578: 28.0.50; [suggestion] allow dired-do-shell-command on directory line Marco Wahl
2020-07-28 18:34 ` Basil L. Contovounesios
2020-07-28 19:09 ` Marco Wahl
2020-07-28 20:20 ` Drew Adams
2020-07-28 21:04 ` Marco Wahl
2020-07-29 7:49 ` Michael Albinus
2020-07-29 11:55 ` Marco Wahl
2020-07-29 12:11 ` Michael Albinus
2020-07-29 12:33 ` Marco Wahl
2020-07-29 14:16 ` Michael Albinus
2020-07-30 10:23 ` Marco Wahl
2020-07-31 14:24 ` Marco Wahl
2020-07-29 0:17 ` arthur miller [this message]
2020-07-29 15:31 ` Drew Adams
2020-07-29 15:59 ` Arthur Miller
2020-07-29 16:29 ` Drew Adams
2020-07-29 18:02 ` Arthur Miller
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=VI1PR06MB452635C56B337968DE8B6D2296700@VI1PR06MB4526.eurprd06.prod.outlook.com \
--to=arthur.miller@live.com \
--cc=42578@debbugs.gnu.org \
--cc=contovob@tcd.ie \
--cc=drew.adams@oracle.com \
--cc=marcowahlsoft@gmail.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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.