[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[elpa] externals/beframe c3e8f88672: Simplify the README; add link to vi
From: |
ELPA Syncer |
Subject: |
[elpa] externals/beframe c3e8f88672: Simplify the README; add link to video demo |
Date: |
Tue, 28 Feb 2023 09:57:19 -0500 (EST) |
branch: externals/beframe
commit c3e8f88672f205b16864ccc184662c47bb5cf8f7
Author: Protesilaos Stavrou <info@protesilaos.com>
Commit: Protesilaos Stavrou <info@protesilaos.com>
Simplify the README; add link to video demo
---
README.md | 14 ++------------
1 file changed, 2 insertions(+), 12 deletions(-)
diff --git a/README.md b/README.md
index bbfc37b50a..7d9e33964b 100644
--- a/README.md
+++ b/README.md
@@ -1,20 +1,10 @@
# Beframe (beframe.el) for GNU Emacs
-Isolate buffers per frame, else "beframe" them.
-
`beframe` enables a frame-oriented Emacs workflow where each frame has
access to the list of buffers visited therein. In the interest of
-brevity, we call buffers that belong to frames "beframed". Beframing
-is achieved in two main ways:
-
-1. By calling the command `beframe-switch-buffer`. It is like the
- standard `switch-to-buffer` except the list of candidates is
- limited to those that the current frame knows about.
+brevity, we call buffers that belong to frames "beframed".
-2. By enabling the global minor mode `beframe-mode`. It sets the
- `read-buffer-function` to one that filters buffers per frame. As
- such, commands like `switch-to-buffer`, `next-buffer`, and
- `previous-buffer` automatically work in a beframed way.
+**Video demo:**
<https://protesilaos.com/codelog/2023-02-28-emacs-beframe-demo/>
+ Package name (GNU ELPA): `beframe`
+ Official manual: <https://protesilaos.com/emacs/beframe>
[Prev in Thread] |
Current Thread |
[Next in Thread] |
- [elpa] externals/beframe c3e8f88672: Simplify the README; add link to video demo,
ELPA Syncer <=