emacs-elpa-diffs
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[elpa] externals-release/activities bf181fa512 019/103: Update FAQ


From: ELPA Syncer
Subject: [elpa] externals-release/activities bf181fa512 019/103: Update FAQ
Date: Tue, 30 Jan 2024 03:57:47 -0500 (EST)

branch: externals-release/activities
commit bf181fa512cab0d3c39daf39fc2ce8fff092acb5
Author: Adam Porter <adam@alphapapa.net>
Commit: Adam Porter <adam@alphapapa.net>

    Update FAQ
---
 README.org | 6 ++++--
 1 file changed, 4 insertions(+), 2 deletions(-)

diff --git a/README.org b/README.org
index 9c256bc66b..9cd2bb02be 100644
--- a/README.org
+++ b/README.org
@@ -46,8 +46,10 @@ If you choose to install it otherwise, you'll need to load 
both the ~activity~ a
 
 + How is this different from 
[[https://github.com/alphapapa/burly.el][Burly.el]] or 
[[https://github.com/alphapapa/bufler.el/][Bufler.el]]? :: Burly is a 
well-polished tool for restoring window and frame configurations, which could 
be considered an incubator for some of the ideas furthered here.  Bufler's 
~bufler-workspace~ library uses Burly to provide some similar functionality, 
which is at an exploratory stage.  ~activity~ hopes to provide a longer-term 
solution more suitable for inte [...]
 
-+ "Activities" haven't seemed to pan out for KDE.  Why would they in Emacs? :: 
KDE Plasma's Activities system requires applications that can save and restore 
their state through Plasma, which only (or mostly only?) KDE apps can do, 
limiting the usefulness of the system.  However, Emacs offers a coherent 
environment, similar to Lisp machines of yore, and its ~bookmarks~ library 
offers a way for any buffer's major mode to save and restore state, if 
implemented (which many already are).
-
 + How does this differ from "workspace" packages? :: Yes, there are many Emacs 
packages that provide "workspace"-like features in one way or another.  To 
date, only Burly and Bufler seem to offer the ability to restore one across 
Emacs sessions.  As mentioned, ~activity~ is intended to be more refined and 
easier to use (e.g. automatically saving activities' states when 
~activity-mode~ is enabled).  Comparisons to other packages are left to the 
reader; suffice to say that ~activity~ is in [...]
 
++ How does this differ from the built-in ~desktop-mode~? :: As best this 
author can tell, ~desktop-mode~ saves and restores one set of buffers, with 
various options to control its behavior.  It does not use ~bookmark~ 
internally, which prevents it from restoring non-file-backed buffers.  As well, 
it is not intended to be used on-demand to switch between sets of buffers, 
windows, or frames (i.e. "activities").
+
++ "Activities" haven't seemed to pan out for KDE.  Why would they in Emacs? :: 
KDE Plasma's Activities system requires applications that can save and restore 
their state through Plasma, which only (or mostly only?) KDE apps can do, 
limiting the usefulness of the system.  However, Emacs offers a coherent 
environment, similar to Lisp machines of yore, and its ~bookmark~ library 
offers a way for any buffer's major mode to save and restore state, if 
implemented (which many already are).
+
 + Why did I get an error? :: Because ~activity~ is at an early stage of 
development and some of these features are not simple to implement.  But it's 
based on Burly, which has already been through much bug-fixing, so it should 
proceed smoothly.  Please report any bugs you find.



reply via email to

[Prev in Thread] Current Thread [Next in Thread]