From: Jean Louis <bugs@gnu.support>
To: help-gnu-emacs@gnu.org
Subject: Re: don't understand setq-default
Date: Mon, 19 Apr 2021 09:52:18 +0300 [thread overview]
Message-ID: <YH0oovmRqnFyf94O@protected.localdomain> (raw)
In-Reply-To: <87wnszj5mj.fsf@zoho.eu>
* Emanuel Berg via Users list for the GNU Emacs text editor <help-gnu-emacs@gnu.org> [2021-04-19 06:50]> Gets soo complicated this just so you can have a bunch of
> buffer instances store some metadata that is common but
> individual. OK, maybe helpful sometimes, sounds like it...
That is what I use all the time over here, for example I search for
people, I can get list of 13 people and mark them, store their ID
numbers in a variable that is same as in other buffer.
In other buffer maybe I mark 2 of them and wish to move them from one
list to other by using buffer, similar like copy/rename in dired.
Let us say there are 2 buffers, you wish to mark 3 people in the list
in one buffer and 4 people in the list in other buffer, but you don't
want to mix them. Their marks go into individual or buffer local
variables that are named same but are different from buffer to buffer.
Buffer 1 would have 3 people with ID numbers like 1, 2 and 3.
Buffer 2 would have 4 people with ID numbers like 23, 28 and 29.
In both cases variable is named `marked-people'
It is possible to switch program execution to other buffer, fetch
those values and switch back.
This may be useful when one needs to merge some information, copy or
rename, probably for many other uses.
One could for example browse a database from Singapore in one buffer,
and other from New York in other buffer and decide to merge some
entries.
--
Jean
Take action in Free Software Foundation campaigns:
https://www.fsf.org/campaigns
Sign an open letter in support of Richard M. Stallman
https://stallmansupport.org/
https://rms-support-letter.github.io/
next prev parent reply other threads:[~2021-04-19 6:52 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-18 11:40 don't understand setq-default Emanuel Berg via Users list for the GNU Emacs text editor
2021-04-18 13:02 ` Omar Polo
2021-04-18 13:39 ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-04-18 13:40 ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-04-18 14:19 ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-04-18 14:59 ` Omar Polo
2021-04-19 3:06 ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-04-19 3:23 ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-04-19 3:33 ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-04-19 6:40 ` Omar Polo
2021-04-19 13:39 ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-04-19 12:49 ` Thibaut Verron
2021-04-19 17:29 ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-04-18 21:59 ` Jean Louis
2021-04-18 22:28 ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-04-19 6:44 ` Jean Louis
2021-04-19 17:17 ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-04-19 3:49 ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-04-19 6:52 ` Jean Louis [this message]
2021-04-19 17:26 ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-04-20 5:44 ` Rounding percentages... was setq-default Jean Louis
2021-04-30 1:04 ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-04-18 21:55 ` don't understand setq-default Jean Louis
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=YH0oovmRqnFyf94O@protected.localdomain \
--to=bugs@gnu.support \
--cc=help-gnu-emacs@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.
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).