unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Dmitry Gutov <dmitry@gutov.dev>
To: Juri Linkov <juri@linkov.net>
Cc: 70996@debbugs.gnu.org, Spencer Baugh <sbaugh@janestreet.com>
Subject: bug#70996: project-find-file defaults
Date: Fri, 14 Jun 2024 20:24:33 +0300	[thread overview]
Message-ID: <773b24ba-43c9-41e0-9f36-f404c07d0fcd@gutov.dev> (raw)
In-Reply-To: <86tthve9y3.fsf@mail.linkov.net>

On 14/06/2024 20:00, Juri Linkov wrote:
>>> I personally never use the file-name-at-point behavior of
>>> project-find-file, but I'm happy with it being higher-precedence because
>>> it will match find-file - as long as it also matches find-file in only
>>> including filenames of existing files.
>> In case you agree with my concerns above (I'm happy to be convinced
>> otherwise), we could try to do something like
>>
>>    (completion-try-completion (thing-at-point 'filename)
>>                               TABLE nil LEN)
> Unfortunately, this might get a false positive on a short word under point
> that with high likelihood will match a file name with a short substring.

It might. But we could set up the styles (or some other way to do the 
matching) so that it would only match full file name segments.





      reply	other threads:[~2024-06-14 17:24 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-17  6:36 bug#70996: project-find-file defaults Juri Linkov
2024-05-28 16:32 ` Juri Linkov
2024-06-08  0:28 ` Dmitry Gutov
2024-06-09 16:51   ` Juri Linkov
2024-06-11  0:02     ` Dmitry Gutov
2024-06-11 16:58       ` Juri Linkov
2024-06-11 20:04         ` Dmitry Gutov
2024-06-12  0:11       ` Spencer Baugh
2024-06-12 13:52         ` Dmitry Gutov
2024-06-12 20:04           ` Dmitry Gutov
2024-06-14 17:00           ` Juri Linkov
2024-06-14 17:24             ` Dmitry Gutov [this message]

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=773b24ba-43c9-41e0-9f36-f404c07d0fcd@gutov.dev \
    --to=dmitry@gutov.dev \
    --cc=70996@debbugs.gnu.org \
    --cc=juri@linkov.net \
    --cc=sbaugh@janestreet.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).