From: Lars Ingebrigtsen <larsi@gnus.org>
To: emacs-devel@gnu.org
Subject: Re: master aae9ac2: Avoid an infloop in shr when filling text with :align-to properties
Date: Fri, 23 Aug 2019 10:39:06 +0200 [thread overview]
Message-ID: <87v9uob7it.fsf@gnus.org> (raw)
In-Reply-To: <20190823065143.0C45320E34@vcs0.savannah.gnu.org> (Lars Ingebrigtsen's message of "Fri, 23 Aug 2019 02:51:42 -0400 (EDT)")
larsi@gnus.org (Lars Ingebrigtsen) writes:
> + (setq d dom)
This reminds me: Aren't there any good ways to get at variables in the
debugger? If you have
;;; -*- lexical-binding: t -*-
(defun foo (bar)
(let ((zot 1))
(debug)))
then you can `e bar RET' to display the value of `bar'. But if you say
`(setq a bar)', you get
Debugger entered--Lisp error: (void-variable bar)
What's up with that?
Furthermore, if you `v' stack line, you get:
foo(t)
bar = t
That's nice, but again there's no way to get at that value that I'm
aware of. This only matters when you have long (and possibly
unprintable) values, of course, but then you have to resort to putting
setqs in the source code, which sucks.
Could we add a command that, when on a variable value, copies the value
into... uhm... a variable prompted for by the command? Sounds pretty
trivial to implement.
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
next prev parent reply other threads:[~2019-08-23 8:39 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20190823065141.21832.91029@vcs0.savannah.gnu.org>
[not found] ` <20190823065143.0C45320E34@vcs0.savannah.gnu.org>
2019-08-23 7:47 ` [Emacs-diffs] master aae9ac2: Avoid an infloop in shr when filling text with :align-to properties Stefan Monnier
2019-08-23 7:59 ` Lars Ingebrigtsen
2019-08-23 8:39 ` Lars Ingebrigtsen [this message]
2019-08-23 9:27 ` Andreas Schwab
2019-08-23 9:29 ` Lars Ingebrigtsen
2019-08-23 12:48 ` Andreas Schwab
2019-08-23 18:46 ` Lars Ingebrigtsen
2019-08-23 20:34 ` Stefan Monnier
2019-08-24 22:56 ` Richard Stallman
2019-08-24 23:15 ` Drew Adams
2019-08-25 5:41 ` Lars Ingebrigtsen
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87v9uob7it.fsf@gnus.org \
--to=larsi@gnus.org \
--cc=emacs-devel@gnu.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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.