From: Sergey Organov <sorganov@gmail.com>
To: Eric S Fraga <e.fraga@ucl.ac.uk>
Cc: emacs-devel@gnu.org
Subject: Re: [ELPA] New package: activities
Date: Sat, 27 Jan 2024 19:14:34 +0300 [thread overview]
Message-ID: <87ede2n47p.fsf@osv.gnss.ru> (raw)
In-Reply-To: <87mssq25ge.fsf@ucl.ac.uk> (Eric S. Fraga's message of "Sat, 27 Jan 2024 14:53:21 +0000")
Eric S Fraga <e.fraga@ucl.ac.uk> writes:
[...]
> I have never found desktop.el to be useful. I do not start emacs from
> different directories so find the whole idea of a desktop counter to my
> use case. I start emacs and then use it for days, working on different
> completely unrelated projects or activities (teaching, coding, writing,
> admin, email, whatever). Emacs, these days, is usually also my window
> manager (exwm).
That's how I use Emacs as well, yet I've built a package based on
deskstop.el and session.el a long time ago that I've called desksess.el,
and I'm still using it.
[...]
> Building on top of desktop.el seems, to me, to be using the wrong
> starting point.
Maybe, maybe not. It was much easier for me to glue two existing
packages together using a bit of simple code than to re-invent the
wheel. Yes, it overrides desktop.el's idea of where to get desktop
files, and which file to load, but that's only a little bit of gluing on
top of rather big package.
> If you believe that new packages should somehow build
> on existing packages, then start with project.el which is more aligned
> to the proposed package. I would love to be able to type
>
> C-x p p <choose project> a
C-c d l <project>
in my case
C-c d l runs the command desksess-load
>
> with "a" for activity, say, taking me back to where I was last with that
> project.
Exactly how desksess.el works, and it loads last visited desktop on
startup, no matter what is current directory.
--
Sergey Organov
next prev parent reply other threads:[~2024-01-27 16:14 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-26 0:59 [ELPA] New package: activities Adam Porter
2024-01-26 7:33 ` Philip Kaludercic
2024-01-26 10:36 ` Adam Porter
2024-01-29 19:50 ` Adam Porter
2024-01-30 7:16 ` Philip Kaludercic
2024-01-30 7:43 ` Adam Porter
2024-01-26 7:45 ` Eli Zaretskii
2024-01-26 10:42 ` Adam Porter
2024-01-26 12:32 ` Eli Zaretskii
2024-01-26 21:59 ` Adam Porter
2024-01-27 7:08 ` Eli Zaretskii
2024-01-27 8:46 ` Adam Porter
2024-01-27 14:53 ` Eric S Fraga
2024-01-27 15:32 ` Eli Zaretskii
2024-01-27 16:14 ` Sergey Organov [this message]
2024-01-28 11:25 ` Eric S Fraga
2024-01-29 10:45 ` Sergey Organov
2024-01-29 13:03 ` Philip Kaludercic
2024-01-29 22:23 ` Sergey Organov
2024-01-29 15:29 ` Fraga, Eric
2024-01-26 8:25 ` Eshel Yaron
2024-01-26 10:48 ` Adam Porter
2024-01-29 21:48 ` JD Smith
2024-01-30 0:08 ` Chris Van Dusen
2024-01-30 0:24 ` Adam Porter
2024-02-01 3:49 ` Richard Stallman
2024-01-30 2:50 ` JD Smith
-- strict thread matches above, loose matches on Subject: below --
2024-01-27 19:20 Drew Adams
2024-02-01 5:33 Joseph Turner
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=87ede2n47p.fsf@osv.gnss.ru \
--to=sorganov@gmail.com \
--cc=e.fraga@ucl.ac.uk \
--cc=emacs-devel@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.