From: Perry Smith <pedz@easesoftware.com>
To: Jean-Christophe Helary <jean.christophe.helary@traduction-libre.org>
Cc: Help Gnu Emacs mailing list <help-gnu-emacs@gnu.org>,
Yuri Khan <yuri.v.khan@gmail.com>
Subject: Re: "grouping" buffers
Date: Sun, 31 May 2020 07:35:58 -0500 [thread overview]
Message-ID: <19B58559-5FB6-41E1-9789-28002A7F6665@easesoftware.com> (raw)
In-Reply-To: <E424373F-3736-44D9-B03E-9B8286F75414@traduction-libre.org>
I don’t what the default ^h-a binding is. It is some restricted form of “apropos”. One thing I do is change this mapping from the default to “apropos”. It gives a more complete list of commands, functions, variables, etc.
(define-key help-map (kbd "a") ‘apropos)
> On May 31, 2020, at 2:34 AM, Jean-Christophe Helary <jean.christophe.helary@traduction-libre.org> wrote:
>
>
>
>> On May 31, 2020, at 16:21, Yuri Khan <yuri.v.khan@gmail.com> wrote:
>>
>>> I don't know how to "set the name frame property". But there is probably a place in the elisp manual that says how to do that.
>>
>> I did this:
>>
>> (set-frame-parameter nil 'name "Hello World!")
>
> Thank you.
>
>> and the title of my WM window that displays the current Emacs frame
>> changed. Of course this made it less convenient: now it displays a
>> static string, whereas previously, per my ‘frame-title-format’
>> configuration, it displayed the unsaved status and name of the buffer
>> in the currently selected window in that frame: •README.md – Emacs.
>
> That's what the manual says. Basically, the name reflects the mode line info. I understand it can be useful, but it's also redundant. Also, I don't need all that when I work with multiple frames. I need to have an idea of what kind of buffers I mainly work with there (hence the subject title: "grouping buffers"). So having a name derived from the *state of the current buffer* in that frame is not useful for me.
>
>> If in your workflow you need a frame that you control, you arrange for
>> your code to create it and stash the reference into a private
>> variable, then refer to the frame via that variable.
>
> I'm not sure what I *need* in technical terms. In practical terms I need to keep the context of a given work, so I want to split my activity between "enclosed" sections of my emacs session. But it looks like the perspective.el mode that I found earlier is close to what I want, so before reinventing a wheel that seems pretty complex, I think I'm going to see how that mode works :)
>
> --
> Jean-Christophe Helary @brandelune
> http://mac4translators.blogspot.com
>
>
next prev parent reply other threads:[~2020-05-31 12:35 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-22 6:26 "grouping" buffers Jean-Christophe Helary
2020-05-27 21:02 ` Douglas Lewan
2020-05-31 3:33 ` Perspectives (was Re: "grouping" buffers) Jean-Christophe Helary
2020-05-27 22:58 ` "grouping" buffers Jakub Jankiewicz
2020-05-31 2:45 ` Jean-Christophe Helary
2020-05-31 3:49 ` Drew Adams
2020-05-31 5:02 ` Jean-Christophe Helary
2020-05-31 7:21 ` Yuri Khan
2020-05-31 7:34 ` Jean-Christophe Helary
2020-05-31 12:35 ` Perry Smith [this message]
2020-05-31 16:39 ` Drew Adams
2020-05-31 14:31 ` Eli Zaretskii
2020-05-31 14:41 ` Jean-Christophe Helary
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=19B58559-5FB6-41E1-9789-28002A7F6665@easesoftware.com \
--to=pedz@easesoftware.com \
--cc=help-gnu-emacs@gnu.org \
--cc=jean.christophe.helary@traduction-libre.org \
--cc=yuri.v.khan@gmail.com \
/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).