From: Christopher Thorne <c.thorne@reckondigital.com>
To: 34621@debbugs.gnu.org
Subject: bug#34621: Patch Update
Date: Tue, 05 Mar 2019 18:22:15 +0000 [thread overview]
Message-ID: <a566d740934418f15ccc286773c5ba17@reckondigital.com> (raw)
In-Reply-To: <f2364e32-6fb6-45e8-b9b7-953f008172c7@default>
> It doesn't sound to me like this has anything, per se,
> to do with Dired. It has to do with how the default is
> determined, and that's apparently now being picked up
> from the buffer name.
Hmm, I think you're right that this isn't just isolated to dired. For
example, I can start a shell-mode buffer, rename it to shell.txt and
rgrep will now suggest "*.txt" as the default extension even though my
buffer is unrelated to .txt files.
An alternative I considered is only showing extension suggestions for
buffers that are associated with a file (i.e. buffer-file-name is a
non-empty string). Can you think of any cases where this would fall
down?
next prev parent reply other threads:[~2019-03-05 18:22 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-22 17:29 bug#34621: [PATCH] lisp/progmodes/grep.el (grep-read-files): Add file-directory-p check Christopher Thorne
2019-03-04 11:13 ` bug#34621: Patch Update Christopher Thorne
2019-03-04 15:26 ` Drew Adams
2019-03-05 10:49 ` Christopher Thorne
2019-03-05 17:48 ` Drew Adams
2019-03-05 18:22 ` Christopher Thorne [this message]
2019-03-05 18:44 ` Drew Adams
2019-03-06 11:10 ` Christopher Thorne
2019-03-17 21:28 ` bug#34621: [PATCH] lisp/progmodes/grep.el (grep-read-files): Add file-directory-p check Juri Linkov
2019-04-08 10:41 ` bug#34621: [PATCH] Fix rgrep in dired taking default search file pattern from directory name (e.g. *.11 for django-1.11) Christopher Thorne
2019-04-08 19:44 ` Juri Linkov
2019-04-09 11:09 ` Christopher Thorne
2019-04-09 11:52 ` Noam Postavsky
2019-04-09 12:23 ` Christopher Thorne
2019-04-09 14:18 ` Eli Zaretskii
2019-04-09 14:32 ` Christopher Thorne
2019-04-09 20:32 ` Juri Linkov
2019-04-10 10:42 ` Christopher Thorne
2019-04-10 20:37 ` Juri Linkov
2019-04-11 20:51 ` Juri Linkov
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=a566d740934418f15ccc286773c5ba17@reckondigital.com \
--to=c.thorne@reckondigital.com \
--cc=34621@debbugs.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.
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.