From: Dmitry Gutov <dgutov@yandex.ru>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: Manuel Uberti <manuel.uberti@inventati.org>,
Stephen Leake <stephen_leake@stephe-leake.org>,
44588@debbugs.gnu.org
Subject: bug#44588: 28.0.50; project-find-file with thing at point
Date: Sun, 15 Nov 2020 00:53:48 +0200 [thread overview]
Message-ID: <867eb27c-eb79-a9f6-88e8-c1ffc23a7600@yandex.ru> (raw)
In-Reply-To: <87blg00xvc.fsf@gnus.org>
On 14.11.2020 17:19, Lars Ingebrigtsen wrote:
> Dmitry Gutov <dgutov@yandex.ru> writes:
>
>> On 12.11.2020 14:34, Lars Ingebrigtsen wrote:
>>> The doc string is trying to say that the string under point is the
>>> default -- it doesn't check that it matches an existing file. I'll
>>> adjust the doc string.
>>
>> Well, the default _is_ (thing-at-point 'filename), though.
>
> Which just looks for a regexp, not whether it's a file that exists.
Right. But a file name doesn't have to describe an existing file to be a
file name. One example: the argument to file-exists-p.
>> I have noticed that too often the picked up default is too long,
>> though. And that clutters up the prompt. Perhaps
>> project--completing-read-strict should shorten it with ellipsis to
>> some predefined width.
>
> It'd be pretty unusual for a prompt to elide bits of the string it's
> actually going to use.
Perhaps.
I wonder if others see the problem I described, and if so whether they
have other suggestions.
prev parent reply other threads:[~2020-11-14 22:53 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-12 9:53 bug#44588: 28.0.50; project-find-file with thing at point Manuel Uberti
2020-11-12 12:34 ` Lars Ingebrigtsen
2020-11-12 13:36 ` Manuel Uberti
2020-11-14 15:17 ` Lars Ingebrigtsen
2020-11-12 13:53 ` Dmitry Gutov
2020-11-14 15:19 ` Lars Ingebrigtsen
2020-11-14 22:53 ` 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=867eb27c-eb79-a9f6-88e8-c1ffc23a7600@yandex.ru \
--to=dgutov@yandex.ru \
--cc=44588@debbugs.gnu.org \
--cc=larsi@gnus.org \
--cc=manuel.uberti@inventati.org \
--cc=stephen_leake@stephe-leake.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.