From: Stefan Kangas <stefan@marxist.se>
To: Juri Linkov <juri@linkov.net>
Cc: Sam Steingold <sds@gnu.org>, 15262@debbugs.gnu.org
Subject: bug#15262: 24.3.50; desktop does not save buffer-display-time
Date: Wed, 21 Aug 2019 23:10:55 +0200 [thread overview]
Message-ID: <CADwFkmkwKmqJZac7-E-=gsPcCd5_PSK=FJ45OETm-Jihnct_ew@mail.gmail.com> (raw)
In-Reply-To: <87pnl2gpu1.fsf@mail.linkov.net>
Juri Linkov <juri@linkov.net> writes:
> > commit cd726ef68ece4fff6772bd08c0051c294e925505
> > Author: Sam Steingold <sds@gnu.org>
> > Date: Sat Oct 15 23:14:48 2016 -0400
> >
> > Save and restore buffer-display-time
> >
> > * desktop.el (desktop-locals-to-save): Add `buffer-display-time'
> > (desktop-read): Set `desktop-file-modtime' before loading the desktop file
> > (desktop-create-buffer): Adjust `buffer-display-time' for the
> > downtime
>
> I used to show buffer-display-time in the customized buffer list.
> After that change buffer-display-time displayed weird times,
> so I had to replace buffer-display-time with visited-file-modtime
> instead. But I think this issue has a minuscule importance,
> so unless somebody wants to add a new attribute inactive-time,
> it was ok to close this.
Thanks for that. What does "customized buffer list" mean here more
exactly? And does this suggest that there is a bug in the above
commit?
Best regards,
Stefan Kangas
next prev parent reply other threads:[~2019-08-21 21:10 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-03 19:09 bug#15262: 24.3.50; desktop does not save buffer-display-time Sam Steingold
2013-09-03 19:26 ` Glenn Morris
2013-09-03 19:46 ` Sam Steingold
2013-09-03 19:51 ` Glenn Morris
2013-09-03 20:04 ` Sam Steingold
2013-09-03 20:30 ` Glenn Morris
2013-09-03 20:39 ` Sam Steingold
2013-09-03 22:55 ` Stefan Monnier
2019-08-18 17:26 ` Stefan Kangas
2019-08-18 20:58 ` Juri Linkov
2019-08-21 21:10 ` Stefan Kangas [this message]
2019-08-21 22:28 ` 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CADwFkmkwKmqJZac7-E-=gsPcCd5_PSK=FJ45OETm-Jihnct_ew@mail.gmail.com' \
--to=stefan@marxist.se \
--cc=15262@debbugs.gnu.org \
--cc=juri@linkov.net \
--cc=sds@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.