From: Dmitry Gutov <dgutov@yandex.ru>
To: Stephen Leake <stephen_leake@stephe-leake.org>, 33618@debbugs.gnu.org
Cc: monnier@IRO.UMontreal.CA
Subject: bug#33618: emacs ada-mode bug 33618
Date: Fri, 21 Dec 2018 02:08:52 +0200 [thread overview]
Message-ID: <58514d4e-12ba-3939-ea40-cfad8c1d44c7@yandex.ru> (raw)
In-Reply-To: <86bm5g3qcp.fsf@stephe-leake.org>
On 20.12.2018 22:17, Stephen Leake wrote:
> Perhaps this bug provides a context to reopen
> that discussion.
Perhaps.
> (project-source-path (project-current)) seems to be the right choice
> here, if we can define that in a reasonable way.
From what I'm seeing of this variable, it doesn't like like a
fundamental property of the project to me personally (*), so I still
think it was the right choice to omit it back then, or at least not base
the file-enumeration logic on it.
(*) None of the environments I work in show error location relative to
some path entries, as opposed to providing either absolute file name, or
file names relative to the current directory.
So I'd like to see more voices from people who do work in such environments.
> Yes, there seems to be a strong preference (bias?) towards only allowing
> a single project per Emacs process.
I'm not sure we should encourage it either. I do know that some users,
at least, open several projects in one Emacs session at the same time.
next prev parent reply other threads:[~2018-12-21 0:08 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-04 23:46 bug#33618: 27.0.50; ada-mode breaks M-x grep Stefan Monnier
2018-12-05 0:02 ` Stefan Monnier
2018-12-05 6:41 ` Eli Zaretskii
2018-12-05 14:26 ` Stefan Monnier
2018-12-05 14:37 ` Eli Zaretskii
2018-12-05 14:41 ` Eli Zaretskii
2018-12-05 16:10 ` Stefan Monnier
2018-12-20 20:17 ` bug#33618: emacs ada-mode bug 33618 Stephen Leake
2018-12-21 0:08 ` Dmitry Gutov [this message]
2018-12-21 23:19 ` bug#33618: update Stephen Leake
2019-01-04 17:27 ` bug#33618: 27.0.50; ada-mode breaks M-x grep Ludovic Brenta
2019-04-20 16:47 ` bug#33618: better fix Stephen Leake
2019-04-20 17:24 ` Eli Zaretskii
2019-04-25 22:52 ` bug#33618: fixed in commit 1486eadf7c9469f873fcd04beafd03f21564d580 Stephen Leake
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=58514d4e-12ba-3939-ea40-cfad8c1d44c7@yandex.ru \
--to=dgutov@yandex.ru \
--cc=33618@debbugs.gnu.org \
--cc=monnier@IRO.UMontreal.CA \
--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 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).