From: Drew Adams <drew.adams@oracle.com>
To: lxsameer <lxsameer@gnu.org>, emacs-devel@gnu.org
Subject: RE: How much I can rely on etc/TODO
Date: Tue, 9 Apr 2019 06:52:00 -0700 (PDT) [thread overview]
Message-ID: <8cc67f8c-081c-48bd-9e2d-792b2ee9d883@default> (raw)
In-Reply-To: <1aeb4b1e-2655-9682-c143-ec1fe0d81a77@gnu.org>
> So is "Give desktop.el a feature to switch between
> different named desktops." still valid ?
Dunno just what was meant by that item, but my
guess is yes, it probably is still valid.
---
Bookmark+ lets you create bookmarks to desktops,
and so switch among them easily. `desktop.el'
still does not let you switch among arbitrary
desktop files AFAIK. But it could...
But this Bookmark+ facility is based partly on
the fact that it has `bmkp-desktop-read', which
lets you load a particular desktop file.
Similarly, function `bmkp-desktop-change-dir'
accepts a desktop file as arg.
`desktop.el' still does not allow this AFAIK.
It's still based on the assumption/restriction
that you can have only one desktop file per
directory.
There's no good reason for this, IMO - a
desktop file could be anywhere. In particular,
there could be multiple desktop files in the
same directory. The directory orientation of
`desktop.el' is an unnecessary encumbrance
(which has never served any useful purpose
AFAIK).
`bmkp-desktop-read' & `bmkp-desktop-change-dir'
are based on `desktop-read' & `desktop-change-dir'.
The difference they offer is to accept a desktop
file as arg. Pretty simple change, but it makes
a big difference in how you can use desktops.
Neither of those `bmkp-*' functions has, itself,
anything to do with bookmarks. They or similar
could easily be added to `desktop.el', to make
desktops and desktop switching more flexible.
That would be a good start toward fulfilling
that TODO wish. It might even be all that's
needed. Well, on its own it doesn't provide
the desktop naming. (Bookmark names provide
that for Bookmark+.) But naming should be
trivial - a start would be to use the desktop
file name or a name derived from it, as
default.
[FWIW, I've mentioned this before, including
years ago.]
https://www.emacswiki.org/emacs/download/bookmark%2b-1.el
next prev parent reply other threads:[~2019-04-09 13:52 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-08 17:52 How much I can rely on etc/TODO Sameer Rahmani
2019-04-08 17:59 ` Eli Zaretskii
2019-04-08 18:26 ` Sameer Rahmani
2019-04-08 20:42 ` Basil L. Contovounesios
2019-04-08 22:14 ` Richard Stallman
2019-04-09 6:03 ` Eli Zaretskii
2019-04-09 7:50 ` lxsameer
2019-04-09 9:39 ` Eli Zaretskii
2019-04-09 12:05 ` Sergey Organov
2019-04-09 13:52 ` Drew Adams [this message]
2019-04-09 23:13 ` Richard Stallman
2019-04-10 15:48 ` Eli Zaretskii
2019-04-10 21:53 ` Richard Stallman
2019-04-11 14:12 ` Eli Zaretskii
-- strict thread matches above, loose matches on Subject: below --
2019-04-11 1:34 Van L
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=8cc67f8c-081c-48bd-9e2d-792b2ee9d883@default \
--to=drew.adams@oracle.com \
--cc=emacs-devel@gnu.org \
--cc=lxsameer@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 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).