From: Noam Postavsky <npostavs@users.sourceforge.net>
To: Andrew Hyatt <ahyatt@gmail.com>
Cc: 5751@debbugs.gnu.org, Arne Schmitz <arne.schmitz@gmx.net>
Subject: bug#5751: Strange behaviour of ff-find-other-file
Date: Mon, 29 Aug 2016 17:55:38 -0400 [thread overview]
Message-ID: <CAM-tV-8iN8P0ugN2sPwQoBeFyyGUbzvJ0tB+x8bG5Pu0E78t6Q@mail.gmail.com> (raw)
In-Reply-To: <CAM6wYYJvAdeXLGy+JDj1D5VSvEMnneQ2K2wxhP+8CLkVKgH3eQ@mail.gmail.com>
On Sun, Aug 28, 2016 at 1:18 AM, Andrew Hyatt <ahyatt@gmail.com> wrote:
>> I'm reopening, because I think this does make sense as a feature
>> request. Generally foo.c and foo.h will be related if they are in the
>> same "project", so probably the user will want the file to be found in
>> this case. I think Emacs recently got some kind of "project API" thing,
>> perhaps that can be used for this?
>
>
> This makes more sense the original proposal, but I'm still not so sure. For
> example, how many projects have multiple directories with files called
> util.c? Probably quite a few. I think any assumptions we make here will be
> bound to cause problems.
>
Probably it will need to be made configurable in the end, but as a
default, I don't think choosing a non-related util.c from another
nearby directory is worse than failing to choose a related one.
prev parent reply other threads:[~2016-08-29 21:55 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-21 19:21 bug#5751: Strange behaviour of ff-find-other-file Arne Schmitz
2016-08-25 4:16 ` Andrew Hyatt
2016-08-26 1:25 ` npostavs
2016-08-28 5:18 ` Andrew Hyatt
2016-08-29 21:55 ` Noam Postavsky [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=CAM-tV-8iN8P0ugN2sPwQoBeFyyGUbzvJ0tB+x8bG5Pu0E78t6Q@mail.gmail.com \
--to=npostavs@users.sourceforge.net \
--cc=5751@debbugs.gnu.org \
--cc=ahyatt@gmail.com \
--cc=arne.schmitz@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).