unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Dmitry Gutov <dgutov@yandex.ru>
To: Manuel Uberti <manuel.uberti@inventati.org>, 49865@debbugs.gnu.org
Subject: bug#49865: 28.0.50; Customize project-find-file without thing-at-pont
Date: Fri, 6 Aug 2021 03:36:06 +0300	[thread overview]
Message-ID: <d092bf87-8295-f692-4963-9dbdb23a1459@yandex.ru> (raw)
In-Reply-To: <8050cc41-2dd3-964b-e6ae-ab267a8a05b9@inventati.org>

Hi Manuel,

Good timing.

On 04.08.2021 09:16, Manuel Uberti wrote:
> when I use project-find-file it always picks up the thing at point even 
> when it is something I am pretty sure that does not correspond to a 
> filename, which, in my case, is all the times.

I have just pushed a patch previously discussed in bug#49204 which 
changes this behavior as well (commit fa89537).

Let me know how you like it. It should make the "thing at point" thing 
less in-your-face, but one could still reach for it when needed.

 > I know that this is not a real bug because I can still type whatever 
I want after calling project-find-file, so I totally understand if this 
is not something worth new code in project.el. It's just that I don't 
see the point for project-find-file to suggest me as defaults things 
like "defun" or "interactive".

Seeing "(default defun): " in the prompt must have been annoying. Though 
I think it was the most problematic when the string at point is long.





  parent reply	other threads:[~2021-08-06  0:36 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-08-04  6:16 bug#49865: 28.0.50; Customize project-find-file without thing-at-pont Manuel Uberti
2021-08-04  8:37 ` Lars Ingebrigtsen
2021-08-04  8:37   ` Lars Ingebrigtsen
2021-08-04  9:07     ` Manuel Uberti
2021-08-06  0:51   ` Dmitry Gutov
2021-08-06  0:36 ` Dmitry Gutov [this message]
2021-08-06  5:27   ` Manuel Uberti
2021-08-06  8:45     ` Dmitry Gutov
2021-08-06  8:51       ` Manuel Uberti
2021-08-06 10:40         ` Lars Ingebrigtsen

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=d092bf87-8295-f692-4963-9dbdb23a1459@yandex.ru \
    --to=dgutov@yandex.ru \
    --cc=49865@debbugs.gnu.org \
    --cc=manuel.uberti@inventati.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 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).