unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Bruno Barbier <brubar.cs@gmail.com>
To: Heime <heimeborgia@protonmail.com>, Emanuel Berg <incal@dataswamp.org>
Cc: help-gnu-emacs@gnu.org
Subject: Re: Initialization warnings without compehensive information about problem
Date: Tue, 15 Nov 2022 18:56:16 +0100	[thread overview]
Message-ID: <6373d14b.5d0a0220.e6a58.255e@mx.google.com> (raw)
In-Reply-To: <b6dSFiXaLRLxaeXkCXg8sRHE173fMPnDtUe6GfMMKtKv2UgTYfWLEOV28bSx91p6abgxHd34VxTiJsSljIxPFh_4l3P4gabaM3yU55K7RCI=@protonmail.com>

Heime <heimeborgia@protonmail.com> writes:

> ------- Original Message -------
> On Sunday, November 13th, 2022 at 3:22 PM, Emanuel Berg <incal@dataswamp.org> wrote:
>
> I would be far more convenient if the "*Warnings*" could provide a little bit
> more information about the problem.  Not at the level of --debug-init or
> byte-compilation, some something one can act on.  

Emacs provides the exact file location and the variable name; I'm not
sure what else I would need.

With the provided information, I would do M-x ffap on the filename to
open it, followed by C-s to find that function name.

Maybe there could be a link to show where that function name occurs, something like:
   (with-current-buffer (find-file "/home/hagbard/.emacs") (occur "wordscal-ktrigr"))



Bruno










      reply	other threads:[~2022-11-15 17:56 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-13 10:34 Initialization warnings without compehensive information about problem Heime
2022-11-13 11:19 ` Emanuel Berg
2022-11-13 14:00 ` Bruno Barbier
2022-11-13 14:57   ` Heime
2022-11-13 15:17     ` Bruno Barbier
2022-11-13 15:22       ` Emanuel Berg
2022-11-15 16:48         ` Heime
2022-11-15 17:56           ` Bruno Barbier [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=6373d14b.5d0a0220.e6a58.255e@mx.google.com \
    --to=brubar.cs@gmail.com \
    --cc=heimeborgia@protonmail.com \
    --cc=help-gnu-emacs@gnu.org \
    --cc=incal@dataswamp.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. 
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).