unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Michael Heerdegen <michael_heerdegen@web.de>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: Phil Sainty <psainty@orcon.net.nz>,
	52290@debbugs.gnu.org, Stefan Monnier <monnier@iro.umontreal.ca>
Subject: bug#52290: 28.0.90; Undocumented generalized variables
Date: Sun, 05 Dec 2021 03:25:12 +0100	[thread overview]
Message-ID: <87ee6rbxfb.fsf@web.de> (raw)
In-Reply-To: <87r1aru7xo.fsf@gnus.org> (Lars Ingebrigtsen's message of "Sun, 05 Dec 2021 03:00:51 +0100")

Lars Ingebrigtsen <larsi@gnus.org> writes:

> I think Stefan had a list of the worst ones...  `point-max', for
> instance, is pretty egregious.  Well, looking at that list -- most of
> are just the worst.  🤐

Ok, `point-max' is not so useful.

I only wanted to note that some generalized vars might be more useful
with `cl-letf' than with plain setf, you get some extra kinds of
excursions gratis (sometimes doesn't work as expected though).  Example:

#+begin_src emacs-lisp
(cl-letf (((cons (point-min) (point-max))
           (cons (line-beginning-position) (line-end-position))))
        (recursive-edit))
#+end_src

Michael.





  reply	other threads:[~2021-12-05  2:25 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-05  1:25 bug#52290: 28.0.90; Undocumented generalized variables Phil Sainty
2021-12-05  1:35 ` Lars Ingebrigtsen
2021-12-05  1:55   ` Michael Heerdegen
2021-12-05  2:00     ` Lars Ingebrigtsen
2021-12-05  2:25       ` Michael Heerdegen [this message]
2021-12-05  2:52         ` Lars Ingebrigtsen
2021-12-05 16:17           ` Michael Heerdegen
2021-12-05 20:43             ` Lars Ingebrigtsen
2021-12-05  2:09   ` Phil Sainty
2021-12-05  2:46     ` Lars Ingebrigtsen
2022-08-21 22:36       ` Lars Ingebrigtsen
2022-08-23  0:07         ` Michael Heerdegen
2022-08-23 10:41           ` Lars Ingebrigtsen
2022-08-31  2:10             ` Michael Heerdegen
2022-08-31  9:58               ` Lars Ingebrigtsen
2022-10-04 11:58         ` Lars Ingebrigtsen
2021-12-06  4:33 ` Richard Stallman

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=87ee6rbxfb.fsf@web.de \
    --to=michael_heerdegen@web.de \
    --cc=52290@debbugs.gnu.org \
    --cc=larsi@gnus.org \
    --cc=monnier@iro.umontreal.ca \
    --cc=psainty@orcon.net.nz \
    /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).