GNU bug report logs -
#11556
24.0.97; Strange behaviour of bury-buffer after desktop-read
Previous Next
Reported by: Tobias Bading <tbading <at> web.de>
Date: Fri, 25 May 2012 08:53:01 UTC
Severity: normal
Found in version 24.0.97
Done: martin rudalics <rudalics <at> gmx.at>
Bug is archived. No further changes may be made.
Full log
Message #16 received at 11556-done <at> debbugs.gnu.org (full text, mbox):
> desktop.diff works fine for me, thank you.
Committed in revision 108018 of the release branch.
> What to expect from desktop-read when used in the middle of a session?
> Good question. I never use it that way, because I tend to spam my one
> and only session with lots of buffers ;-). However, other more
> organized people might use multiple desktop files. They would probably
> want desktop-read to behave as in Emacs 23, whatever that behaviour
> exactly was.
I don't use desktop but wonder what should happen when, for example, a
buffer read by `desktop-read' exists already. Should it move to the
front of the buffer lists or stay where it was before?
> The "If no desktop file is found, clear the desktop
> [...]" part in the doc-string of desktop-read sounds odd to me. Why
> would the function want to clear the desktop if it doesn't find a
> desktop file, but perform some sort of a merge operation with the
> current session (instead of a replace) if one is found?
Looks odd. Anyone who wants to clear the desktop could do this by
calling `desktop-clear'.
I'm looking for a kind soul to work on integrating window handling into
desktop.
martin
This bug report was last modified 13 years and 77 days ago.
Previous Next
GNU bug tracking system
Copyright (C) 1999 Darren O. Benham,
1997,2003 nCipher Corporation Ltd,
1994-97 Ian Jackson.