From: Uwe Brauer <oub@mat.ucm.es>
To: help-gnu-emacs@gnu.org
Subject: Re: problems with better-registers: turn-off-all-minor modes or remove all text-properties
Date: Sun, 24 Jul 2022 07:39:02 +0200 [thread overview]
Message-ID: <87wnc31349.fsf@mat.ucm.es> (raw)
In-Reply-To: 87sfmrma82.fsf@web.de
[-- Attachment #1: Type: text/plain, Size: 1554 bytes --]
>>> "MH" == Michael Heerdegen <michael_heerdegen@web.de> writes:
> Michael Heerdegen <michael_heerdegen@web.de> writes:
>> Could you please be more specific - what's the problem? As Stefan said,
>> text properties are normally not a problem in this case.
> Ok, after reading again what you had posted in emacs-dev, I saw your
> string contained unreadable properties. Your string contained a button,
> for example.
> What I would do is to advice `set-register' to strip unreadable
> properties from any stringp value. Or just strip text properties if you
> don't want them anyway. That's better than trying to work around that
> problem.
Thanks, that did not occur to me. I tried to advice since a while since
it makes debugging difficult.
In any case, maybe because I have not used it for a while, my attempts
failed:
(defadvice set-property (before removeproperties activate)
"Remove all text properties before setting the property"
(let ((inhibit-read-only t))
(set-text-properties (point-min) (point-max) nil)))
(defadvice set-property (after removeproperties activate)
"Remove all text properties before setting the property"
(let ((inhibit-read-only t))
(set-text-properties (point-min) (point-max) nil)))
None of them worked
Any ideas?
thanks
Uwe Brauer
--
I strongly condemn Putin's war of aggression against the Ukraine.
I support to deliver weapons to Ukraine's military.
I support the ban of Russia from SWIFT.
I support the EU membership of the Ukraine.
[-- Attachment #2: smime.p7s --]
[-- Type: application/pkcs7-signature, Size: 5673 bytes --]
next prev parent reply other threads:[~2022-07-24 5:39 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-23 16:45 problems with better-registers: turn-off-all-minor modes or remove all text-properties Uwe Brauer
2022-07-23 20:35 ` Thorsten Bonow
2022-07-24 0:09 ` Michael Heerdegen
2022-07-24 3:59 ` Michael Heerdegen
2022-07-24 5:39 ` Uwe Brauer [this message]
2022-07-24 19:51 ` [SOLVED] (was: problems with better-registers: turn-off-all-minor modes or remove all text-properties) Uwe Brauer
2022-07-24 22:36 ` [SOLVED] Michael Heerdegen
2022-07-25 5:37 ` [SOLVED] Uwe Brauer
2022-07-25 5:49 ` [SOLVED] Uwe Brauer
2022-07-25 17:09 ` [SOLVED] Stefan Monnier via Users list for the GNU Emacs text editor
2022-07-25 19:49 ` [SOLVED] Uwe Brauer
2022-07-25 22:37 ` [SOLVED] Michael Heerdegen
2022-07-26 4:57 ` [SOLVED] Uwe Brauer
2022-07-26 13:01 ` [SOLVED] Thorsten Bonow
2022-07-26 15:02 ` [SOLVED] Uwe Brauer
2022-07-26 16:23 ` [SOLVED] Yuri Khan
2022-07-26 23:28 ` [SOLVED] Michael Heerdegen
2022-07-27 10:50 ` [SOLVED] Uwe Brauer
2022-07-27 15:04 ` [SOLVED] Yuri Khan
2022-07-28 14:46 ` [SOLVED$ Uwe Brauer
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=87wnc31349.fsf@mat.ucm.es \
--to=oub@mat.ucm.es \
--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).