[Top][All Lists]

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

Re: "grouping" buffers

From: Perry Smith
Subject: Re: "grouping" buffers
Date: Sun, 31 May 2020 07:35:58 -0500

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, 

    (define-key help-map (kbd "a") ‘apropos)

> On May 31, 2020, at 2:34 AM, Jean-Christophe Helary 
> <> wrote:
>> On May 31, 2020, at 16:21, Yuri Khan <> 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: • – 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

reply via email to

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