unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Juri Linkov <juri@linkov.net>
Cc: 62447@debbugs.gnu.org, manuel@ledu-giraud.fr
Subject: bug#62447: 30.0.50; xref default behaviour changed after a desktop-read
Date: Sun, 26 Mar 2023 07:25:17 +0300	[thread overview]
Message-ID: <83bkkgb0lu.fsf@gnu.org> (raw)
In-Reply-To: <86355smy5i.fsf@mail.linkov.net> (message from Juri Linkov on Sat, 25 Mar 2023 21:25:13 +0200)

> Cc: 62447@debbugs.gnu.org
> From: Juri Linkov <juri@linkov.net>
> Date: Sat, 25 Mar 2023 21:25:13 +0200
> 
> > I'm using desktop-save-mode and since sometimes when I do a M-. on
> > function call in a C buffer, Emacs says:
> > user-error: No definitions found for: scroll_command
> >
> > If I start without desktop-save-mode on, this works as usual: Emacs asks
> > me if I want to read the TAGS table.
> >
> > So it may be that some mode loaded by some file opening mess up with
> > xref default behaviour... I don't know where to start to track this
> > down.
> 
> I guess this is because the default value of `desktop-globals-to-save'
> contains:
> 
>     tags-file-name
>     tags-table-list
> 
> and the global values for these variables make no sense.

Why not?  How is TAGS different from any other file visited by Emacs,
with respect to desktop-save-mode?

> They should have project-local values, but project-local values are
> not saved to the desktop file, only global and buffer-local values.

We don't force our users to use project.el in order to have some
file-visiting buffers to be saved in the desktop file.  E.g., I don't
use project.el, but I do use TAGS all the time, in particular with
Emacs.  Emacs supports lists of TAGS tables since time immemoriam, to
let users use M-. and friends with more than a single program.





      parent reply	other threads:[~2023-03-26  4:25 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-25 18:39 bug#62447: 30.0.50; xref default behaviour changed after a desktop-read Manuel Giraud via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-03-25 18:53 ` Eli Zaretskii
2023-03-25 22:04   ` Manuel Giraud via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-03-25 19:25 ` Juri Linkov
2023-03-25 22:13   ` Manuel Giraud via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-03-25 22:50     ` Manuel Giraud via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-03-26  4:57     ` Eli Zaretskii
2023-03-26  9:51       ` Manuel Giraud via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-09-12  0:00         ` Stefan Kangas
2023-03-26  4:25   ` Eli Zaretskii [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=83bkkgb0lu.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=62447@debbugs.gnu.org \
    --cc=juri@linkov.net \
    --cc=manuel@ledu-giraud.fr \
    /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).