unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Drew Adams <drew.adams@oracle.com>
To: Manuel Giraud <manuel@ledu-giraud.fr>
Cc: "62096@debbugs.gnu.org" <62096@debbugs.gnu.org>,
	Stephen Berman <stephen.berman@gmx.net>
Subject: bug#62096: 30.0.50; find-dired, dired-goto-file and spaces
Date: Fri, 10 Mar 2023 21:24:33 +0000	[thread overview]
Message-ID: <SJ0PR10MB5488DF48EAC6EE1880CD8780F3BA9@SJ0PR10MB5488.namprd10.prod.outlook.com> (raw)
In-Reply-To: <87356c8hja.fsf@ledu-giraud.fr>

> > In my tests with `emacs -Q`, `dired-listing-switches' is
> > just "-al", so I'm guessing that going down this road
> > isn't the right approach (isn't sufficient).
> 
> Ok.  And what do you have as 'find-ls-option-default-ls' and
> 'system-type'?

`system-type': windows-nt

`find-ls-option-default-ls': In 28.2, ("-ls" . "-dilsb").
In 26.3 there's no such var.


But I should say that I cheated.  For `emacs -Q' I didn't
bother to try to set up Cygwin etc. and actually use
`find-name-dired'.

I just copied the buffer text from my use of `find-name-dired'
in my own setup into a virgin buffer, put that in `dired-mode',
and copied the value of dired-subdir-alist from the find output
buffer in my setup: 
(setq dired-subdir-alist '(("path/to/dir/" . 1)))

So I can't make a solid claim about this.





  reply	other threads:[~2023-03-10 21:24 UTC|newest]

Thread overview: 52+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-10 14:54 bug#62096: 30.0.50; find-dired, dired-goto-file and spaces Manuel Giraud via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-03-10 15:43 ` Drew Adams
2023-03-10 15:59   ` Stephen Berman
2023-03-10 17:10     ` Drew Adams
2023-03-10 18:07     ` Manuel Giraud via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-03-10 18:37       ` Manuel Giraud via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-03-10 20:48         ` Daniel Martín via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-03-10 21:04           ` Manuel Giraud via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-03-11  0:14             ` Daniel Martín via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-03-11 14:02               ` Manuel Giraud via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-03-11 14:17                 ` Eli Zaretskii
2023-03-11 14:27                   ` Manuel Giraud via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-03-17  7:49                     ` Manuel Giraud via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-03-17  8:33                       ` Eli Zaretskii
2023-03-17  9:12                         ` Manuel Giraud via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-03-17 11:33                           ` Eli Zaretskii
2023-03-17 15:25                             ` Drew Adams
2023-03-17 15:41                               ` Manuel Giraud via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-03-17 16:14                                 ` Drew Adams
2023-03-17 16:26                               ` Eli Zaretskii
2023-03-17 17:20                                 ` Drew Adams
2023-03-17 17:50                                   ` Manuel Giraud via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-03-17 18:56                                     ` Eli Zaretskii
2023-03-17 18:42                                   ` Eli Zaretskii
2023-03-17 17:54                             ` Manuel Giraud via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-03-17 18:57                               ` Eli Zaretskii
2023-03-17 19:10                                 ` Manuel Giraud via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-03-18  6:34                                   ` Eli Zaretskii
2023-03-18 10:16                                     ` Manuel Giraud via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-03-12 10:54                   ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-03-12 11:32                     ` Eli Zaretskii
2023-03-12 11:56                       ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-03-12 17:51                     ` Manuel Giraud via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-03-11 17:09                 ` Daniel Martín via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-03-11 18:46                   ` Manuel Giraud via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-03-11 19:30                     ` Daniel Martín via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-03-10 21:31           ` Drew Adams
2023-03-10 21:43             ` Manuel Giraud via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-03-11 12:00           ` Eli Zaretskii
2023-03-12 10:55           ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-03-11 11:55         ` Eli Zaretskii
2023-03-11 14:12           ` Manuel Giraud via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-03-10 19:05       ` Manuel Giraud via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-03-10 19:55         ` Drew Adams
2023-03-10 20:42           ` Manuel Giraud via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-03-10 21:24             ` Drew Adams [this message]
2023-03-10 21:32               ` Manuel Giraud via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-03-10 21:45                 ` Drew Adams
2023-03-10 22:03                   ` Manuel Giraud via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-03-10 22:20                     ` Drew Adams
2023-03-11 11:58         ` Eli Zaretskii
2023-03-10 19:48       ` Drew Adams

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=SJ0PR10MB5488DF48EAC6EE1880CD8780F3BA9@SJ0PR10MB5488.namprd10.prod.outlook.com \
    --to=drew.adams@oracle.com \
    --cc=62096@debbugs.gnu.org \
    --cc=manuel@ledu-giraud.fr \
    --cc=stephen.berman@gmx.net \
    /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).