From: 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: Thu, 25 Aug 2016 21:25:54 -0400 [thread overview]
Message-ID: <877fb4tj6l.fsf@users.sourceforge.net> (raw)
In-Reply-To: <m2shttzdod.fsf@Andrews-MacBook-Pro.local> (Andrew Hyatt's message of "Thu, 25 Aug 2016 00:16:02 -0400")
reopen 5751
tags 5751 - notabug
severity 5751 wishlist
retitle 5751 Let ff-find-other-file search other directories (in "project"?)
quit
Andrew Hyatt <ahyatt@gmail.com> writes:
> Sorry for the delay in response here. I think I understand what you are
> saying, but I think we probably would both agree this is more of a
> feature request than a bug.
>
> But I'm not sure it makes sense as a feature request - just because you
> have foo.c and foo.h, it is dangerous to think they are related just
> because they both exist as buffers. I frequently have multiple copies
> of the same file open in different directories to work on different
> issues - it would be a bug if ff-find-other-file started flipping
> between two very different working directories.
>
> So, I'm closing this one as not a bug.
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?
next prev parent reply other threads:[~2016-08-26 1:25 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 [this message]
2016-08-28 5:18 ` Andrew Hyatt
2016-08-29 21:55 ` Noam Postavsky
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=877fb4tj6l.fsf@users.sourceforge.net \
--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).