From: Eli Zaretskii <eliz@gnu.org>
To: help-gnu-emacs@gnu.org
Subject: Re: What should I use to unrestrict a buffer?
Date: Thu, 25 Jan 2024 09:14:26 +0200 [thread overview]
Message-ID: <86r0i5dgvh.fsf@gnu.org> (raw)
In-Reply-To: <4df85194384c642c3cda3289cd1ac1a20ee42bcc.camel@adminart.net> (message from hw on Wed, 24 Jan 2024 21:12:56 +0100)
> From: hw <hw@adminart.net>
> Date: Wed, 24 Jan 2024 21:12:56 +0100
>
> Also, I don't want possible restrictions to be restored, like
> (without-restriction) would do.
Why not? After you do whatever you need to do with the widened
buffer, you are supposed to return the restrictions to their previous
state, and that includes restoring the restrictions present before the
widening. Why would you need to avoid restoring them, and thus change
the restrictions behind some other Lisp program which doesn't expect
its restrictions to be lifted?
next prev parent reply other threads:[~2024-01-25 7:14 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-24 20:12 What should I use to unrestrict a buffer? hw
2024-01-25 7:14 ` Eli Zaretskii [this message]
2024-01-25 18:30 ` hw
2024-01-25 19:03 ` Eli Zaretskii
2024-02-08 5:38 ` hw
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=86r0i5dgvh.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=help-gnu-emacs@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.
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).