From: Filipp Gunbin <fgunbin@fastmail.fm>
To: Arthur Miller <arthur.miller@live.com>
Cc: 48883@debbugs.gnu.org, Boruch Baum <boruch_baum@gmx.com>
Subject: bug#48883: dired marking bugs
Date: Tue, 08 Jun 2021 03:32:39 +0300 [thread overview]
Message-ID: <m2sg1tnql4.fsf@fastmail.fm> (raw)
In-Reply-To: <AM9PR09MB4977CD34ACB8CB27266FC14296389@AM9PR09MB4977.eurprd09.prod.outlook.com> (Arthur Miller's message of "Mon, 07 Jun 2021 20:53:02 +0200")
On 07/06/2021 20:53 +0200, Arthur Miller wrote:
> Boruch Baum <boruch_baum@gmx.com> writes:
>
>> In testing my diredc package, I'm coming across the following bugs
>> reproducable in \emacs -Q -nw:
>>
>> 1) Improper marking of directory heading line
>>
>> 1.1) The correct and expected behavior of dired is that when one
>> navigates to a directory heading line (eg. the first line of a
>> simple dired buffer) and presses 'm', all "real" files of that
>> directory are marked, [IMPORTANT] the lines for the "not-real"
>> files '.' and '..' are not marked, and [IMPORTANT] the directory
>> line itself is not marked.
> I have no idea if that is "correct and expected behaviour", I don't see
> it said in manual, or I missed it, but anyway, the headline in Dired is
> a waste of space since you can see dir name in modeline or frame title,
> [...]
The headlines are very much needed if you have -R in ls switches…
next prev parent reply other threads:[~2021-06-08 0:32 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-06 20:33 bug#48883: dired marking bugs Boruch Baum
2021-06-06 22:12 ` bug#48883: [External] : " Drew Adams
2021-06-06 22:44 ` Boruch Baum
2021-06-07 15:24 ` Drew Adams
2021-06-07 0:08 ` Boruch Baum
2021-06-07 15:21 ` Drew Adams
2021-06-07 16:16 ` Drew Adams
2021-06-07 0:50 ` Boruch Baum
2021-06-07 18:53 ` Arthur Miller
2021-06-08 0:32 ` Filipp Gunbin [this message]
2021-06-08 4:15 ` Arthur Miller
2021-06-08 12:41 ` Filipp Gunbin
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=m2sg1tnql4.fsf@fastmail.fm \
--to=fgunbin@fastmail.fm \
--cc=48883@debbugs.gnu.org \
--cc=arthur.miller@live.com \
--cc=boruch_baum@gmx.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 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).