unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
* Emacs messages
@ 2021-05-04  5:48 Christopher Dimech
  2021-05-04  7:06 ` Emanuel Berg via Emacs development discussions.
  2021-05-04 11:49 ` Eli Zaretskii
  0 siblings, 2 replies; 10+ messages in thread
From: Christopher Dimech @ 2021-05-04  5:48 UTC (permalink / raw)
  To: emacs-devel

Dear Compeers, 

I have an extensive number of .el files I use to customise emacs.
A few moments ago I made changes to the code and kept one variable
unmodified as `sel' rather than using `selection'.

Emacs complained with

  cond: Symbol’s value as variable is void: sel

It would be instructive for users if emacs include additional information,
like the file name and line number associated with the detected `cond' problem.

Regards
Christopher




^ permalink raw reply	[flat|nested] 10+ messages in thread

* Re: Emacs messages
  2021-05-04  5:48 Emacs messages Christopher Dimech
@ 2021-05-04  7:06 ` Emanuel Berg via Emacs development discussions.
  2021-05-04 11:49 ` Eli Zaretskii
  1 sibling, 0 replies; 10+ messages in thread
From: Emanuel Berg via Emacs development discussions. @ 2021-05-04  7:06 UTC (permalink / raw)
  To: emacs-devel

Christopher Dimech wrote:

> I have an extensive number of .el files I use to customise
> emacs. A few moments ago I made changes to the code and kept
> one variable unmodified as `sel' rather than using
> `selection'.
>
> Emacs complained with
>
>   cond: Symbol’s value as variable is void: sel
>
> It would be instructive for users if emacs include
> additional information, like the file name and line number
> associated with the detected `cond' problem.

Did you byte-compile the source? Helps.

-- 
underground experts united
https://dataswamp.org/~incal




^ permalink raw reply	[flat|nested] 10+ messages in thread

* Re: Emacs messages
  2021-05-04  5:48 Emacs messages Christopher Dimech
  2021-05-04  7:06 ` Emanuel Berg via Emacs development discussions.
@ 2021-05-04 11:49 ` Eli Zaretskii
  2021-05-04 12:33   ` Christopher Dimech
  1 sibling, 1 reply; 10+ messages in thread
From: Eli Zaretskii @ 2021-05-04 11:49 UTC (permalink / raw)
  To: Christopher Dimech; +Cc: emacs-devel

> From: Christopher Dimech <dimech@gmx.com>
> Date: Tue, 4 May 2021 07:48:12 +0200
> Sensitivity: Normal
> 
> I have an extensive number of .el files I use to customise emacs.
> A few moments ago I made changes to the code and kept one variable
> unmodified as `sel' rather than using `selection'.
> 
> Emacs complained with
> 
>   cond: Symbol’s value as variable is void: sel
> 
> It would be instructive for users if emacs include additional information,
> like the file name and line number associated with the detected `cond' problem.

Emacs does that if you set debug-on-error non-nil, the you will have
the backtrace from which you can jump to the offending source.



^ permalink raw reply	[flat|nested] 10+ messages in thread

* Re: Emacs messages
  2021-05-04 11:49 ` Eli Zaretskii
@ 2021-05-04 12:33   ` Christopher Dimech
  2021-05-04 12:43     ` Eli Zaretskii
  0 siblings, 1 reply; 10+ messages in thread
From: Christopher Dimech @ 2021-05-04 12:33 UTC (permalink / raw)
  To: Eli Zaretskii; +Cc: emacs-devel

This is what I get.  Cannot see the file name.  Particularly important would
be the path when one is keeping different versions of the code.

--------

Debugger entered--Lisp error: (void-variable selc)
  (equal selc '"+")
  (cond ((equal selc '"+") (set (make-local-variable 'ricci-deviat) '(0.18 -0.18)) (set (make-local-variable 'ricci-scale) 0.2)) ((equal selc '"-") (set (make-local-variable 'ricci-deviat) '(0.0 0.0)) (set (make-local-variable 'ricci-scale) 1.0)) (t nil))
  ricci-notation("+")
  ricci-notation-enable()
  (cond ((eql crucibulum-sweep-kondor 1) (ricci-notation-enable) (message "[fadeev-crucibulum] (+) ricci notation") (set (make-local-variable 'crucibulum-sweep-kondor) (1+ crucibulum-sweep-kondor))) ((eql crucibulum-sweep-kondor 2) (ideogram-vision-enable) (message "[faddeev-crucibulum] (+) ricci notation (+) ideogr...") (set (make-local-variable 'crucibulum-sweep-kondor) (1+ crucibulum-sweep-kondor))) (t (ricci-notation-disable) (ideogram-vision-disable) (message "[faddeev-crucibulum] (-) ricci notation (-) ideogr...") (set (make-local-variable 'crucibulum-sweep-kondor) 1)))
  crucibulum-sweep()
  funcall-interactively(crucibulum-sweep)
  call-interactively(crucibulum-sweep nil nil)
  command-execute(crucibulum-sweep)





^ permalink raw reply	[flat|nested] 10+ messages in thread

* Re: Emacs messages
  2021-05-04 12:33   ` Christopher Dimech
@ 2021-05-04 12:43     ` Eli Zaretskii
  2021-05-04 12:52       ` Christopher Dimech
  2021-05-04 12:57       ` Christopher Dimech
  0 siblings, 2 replies; 10+ messages in thread
From: Eli Zaretskii @ 2021-05-04 12:43 UTC (permalink / raw)
  To: Christopher Dimech; +Cc: emacs-devel

> From: Christopher Dimech <dimech@gmx.com>
> Cc: emacs-devel@gnu.org
> Date: Tue, 4 May 2021 14:33:37 +0200
> Sensitivity: Normal
> 
> This is what I get.  Cannot see the file name.

Click on a line in the backtrace, and you will be taken to the file.



^ permalink raw reply	[flat|nested] 10+ messages in thread

* Re: Emacs messages
  2021-05-04 12:43     ` Eli Zaretskii
@ 2021-05-04 12:52       ` Christopher Dimech
  2021-05-04 12:57       ` Christopher Dimech
  1 sibling, 0 replies; 10+ messages in thread
From: Christopher Dimech @ 2021-05-04 12:52 UTC (permalink / raw)
  To: Eli Zaretskii; +Cc: emacs-devel

I can see the path from the modeline.


> Sent: Wednesday, May 05, 2021 at 12:43 AM
> From: "Eli Zaretskii" <eliz@gnu.org>
> To: "Christopher Dimech" <dimech@gmx.com>
> Cc: emacs-devel@gnu.org
> Subject: Re: Emacs messages
>
> > From: Christopher Dimech <dimech@gmx.com>
> > Cc: emacs-devel@gnu.org
> > Date: Tue, 4 May 2021 14:33:37 +0200
> > Sensitivity: Normal
> >
> > This is what I get.  Cannot see the file name.
>
> Click on a line in the backtrace, and you will be taken to the file.
>



^ permalink raw reply	[flat|nested] 10+ messages in thread

* Re: Emacs messages
  2021-05-04 12:43     ` Eli Zaretskii
  2021-05-04 12:52       ` Christopher Dimech
@ 2021-05-04 12:57       ` Christopher Dimech
  2021-05-04 13:02         ` Eli Zaretskii
  1 sibling, 1 reply; 10+ messages in thread
From: Christopher Dimech @ 2021-05-04 12:57 UTC (permalink / raw)
  To: Eli Zaretskii; +Cc: emacs-devel

When using "debug-on-message", what messages would be useful to include?



> Sent: Wednesday, May 05, 2021 at 12:43 AM
> From: "Eli Zaretskii" <eliz@gnu.org>
> To: "Christopher Dimech" <dimech@gmx.com>
> Cc: emacs-devel@gnu.org
> Subject: Re: Emacs messages
>
> > From: Christopher Dimech <dimech@gmx.com>
> > Cc: emacs-devel@gnu.org
> > Date: Tue, 4 May 2021 14:33:37 +0200
> > Sensitivity: Normal
> >
> > This is what I get.  Cannot see the file name.
>
> Click on a line in the backtrace, and you will be taken to the file.
>
>



^ permalink raw reply	[flat|nested] 10+ messages in thread

* Re: Emacs messages
  2021-05-04 12:57       ` Christopher Dimech
@ 2021-05-04 13:02         ` Eli Zaretskii
  2021-05-04 13:08           ` Christopher Dimech
  0 siblings, 1 reply; 10+ messages in thread
From: Eli Zaretskii @ 2021-05-04 13:02 UTC (permalink / raw)
  To: Christopher Dimech; +Cc: emacs-devel

> From: Christopher Dimech <dimech@gmx.com>
> Cc: emacs-devel@gnu.org
> Date: Tue, 4 May 2021 14:57:52 +0200
> 
> When using "debug-on-message", what messages would be useful to include?

The error message that Emacs displays.



^ permalink raw reply	[flat|nested] 10+ messages in thread

* Re: Emacs messages
  2021-05-04 13:02         ` Eli Zaretskii
@ 2021-05-04 13:08           ` Christopher Dimech
  2021-05-04 13:59             ` Eli Zaretskii
  0 siblings, 1 reply; 10+ messages in thread
From: Christopher Dimech @ 2021-05-04 13:08 UTC (permalink / raw)
  To: Eli Zaretskii; +Cc: emacs-devel

> Sent: Wednesday, May 05, 2021 at 1:02 AM
> From: "Eli Zaretskii" <eliz@gnu.org>
> To: "Christopher Dimech" <dimech@gmx.com>
> Cc: emacs-devel@gnu.org
> Subject: Re: Emacs messages
>
> > From: Christopher Dimech <dimech@gmx.com>
> > Cc: emacs-devel@gnu.org
> > Date: Tue, 4 May 2021 14:57:52 +0200
> >
> > When using "debug-on-message", what messages would be useful to include?
>
> The error message that Emacs displays.

Thusly, for "debug-on-message", you has to wait for emacs to tell you.  No point in
presetting any?  Perhaps some frequently encountered messages?




^ permalink raw reply	[flat|nested] 10+ messages in thread

* Re: Emacs messages
  2021-05-04 13:08           ` Christopher Dimech
@ 2021-05-04 13:59             ` Eli Zaretskii
  0 siblings, 0 replies; 10+ messages in thread
From: Eli Zaretskii @ 2021-05-04 13:59 UTC (permalink / raw)
  To: Christopher Dimech; +Cc: emacs-devel

> From: Christopher Dimech <dimech@gmx.com>
> Cc: emacs-devel@gnu.org
> Date: Tue, 4 May 2021 15:08:38 +0200
> 
> > > When using "debug-on-message", what messages would be useful to include?
> >
> > The error message that Emacs displays.
> 
> Thusly, for "debug-on-message", you has to wait for emacs to tell you.  No point in
> presetting any?  Perhaps some frequently encountered messages?

That variable's main use case is when you already know which message
you want to trigger it, or can guess.



^ permalink raw reply	[flat|nested] 10+ messages in thread

end of thread, other threads:[~2021-05-04 13:59 UTC | newest]

Thread overview: 10+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2021-05-04  5:48 Emacs messages Christopher Dimech
2021-05-04  7:06 ` Emanuel Berg via Emacs development discussions.
2021-05-04 11:49 ` Eli Zaretskii
2021-05-04 12:33   ` Christopher Dimech
2021-05-04 12:43     ` Eli Zaretskii
2021-05-04 12:52       ` Christopher Dimech
2021-05-04 12:57       ` Christopher Dimech
2021-05-04 13:02         ` Eli Zaretskii
2021-05-04 13:08           ` Christopher Dimech
2021-05-04 13:59             ` Eli Zaretskii

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).