unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Noam Postavsky <npostavs@gmail.com>
To: Juri Linkov <juri@linkov.net>
Cc: 30786@debbugs.gnu.org
Subject: bug#30786: Save text properties in desktop
Date: Mon, 12 Mar 2018 21:16:40 -0400	[thread overview]
Message-ID: <87o9jsydtz.fsf@gmail.com> (raw)
In-Reply-To: <87k1uhnehk.fsf@mail.linkov.net> (Juri Linkov's message of "Mon,  12 Mar 2018 23:57:59 +0200")

Juri Linkov <juri@linkov.net> writes:

> Why does desktop.el not save text properties?
> Maybe for some historical reasons?
> This is required for bug#22479.
> I can't find a problem while trying this patch:

> -     (let ((copy (copy-sequence value)))
> -       (set-text-properties 0 (length copy) nil copy)
> -       ;; Get rid of text properties because we cannot read them.

I guess this comment is relevant, you can easily have non-readable
property values, e.g.: (put-text-property 1 2 'foo (point-marker)).
Maybe solving Bug#24982 would help?





  reply	other threads:[~2018-03-13  1:16 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-03-12 21:57 bug#30786: Save text properties in desktop Juri Linkov
2018-03-13  1:16 ` Noam Postavsky [this message]
2018-03-13 21:52   ` Juri Linkov
2018-03-14  1:09     ` Drew Adams
2018-03-14  2:37       ` Noam Postavsky
2018-03-14 20:09         ` Drew Adams
2018-04-02 19:41         ` Juri Linkov
2018-04-02 21:48           ` Noam Postavsky
2018-04-03 20:11             ` Juri Linkov
2018-04-03 22:01               ` Noam Postavsky
2018-04-04 20:01                 ` Juri Linkov
2018-04-07 13:08                   ` Noam Postavsky
2018-04-07 20:46                     ` Juri Linkov
2018-04-08  1:54                       ` Noam Postavsky
2018-04-08 20:13                         ` Juri Linkov
2018-04-19 20:32                           ` Juri Linkov

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=87o9jsydtz.fsf@gmail.com \
    --to=npostavs@gmail.com \
    --cc=30786@debbugs.gnu.org \
    --cc=juri@linkov.net \
    /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).