unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: TRS-80 <lists.trs-80@isnotmyreal.name>
To: help-gnu-emacs@gnu.org
Subject: Re: display-buffer-alist actions
Date: Wed, 24 Feb 2021 16:08:38 -0500	[thread overview]
Message-ID: <2196a99d653eab281dc8c3f97ca405cb@isnotmyreal.name> (raw)
In-Reply-To: <87h7m1tefq.fsf@fastmail.fm>

On 2021-02-24 15:08, Joost Kremers wrote:
> On Wed, Feb 24 2021, Joost Kremers wrote:
>> On Wed, Feb 24 2021, Eric S Fraga wrote:
>>> I've read and re-read the documentation for display-buffer-alist and 
>>> I
>>> cannot quite understand it.
>> 
>> Yes, it's the easiest thing to grok.
> 
> Of course I meant it's *not* the easiest thing to grok...

I was going to say, I don't think even jwz understands it...

:D

I will check out the video.  Or maybe it was that video that got me to
try it in the first place.  I don't remember now.  Anyway, Prot is
great.  :)

I seem to recall just playing with some of the options to see what they
did, until I eventually I found a couple that did whatever it was I was
trying to do at the time.

Cheers,
TRS-80



  reply	other threads:[~2021-02-24 21:08 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-24 17:44 display-buffer-alist actions Eric S Fraga
2021-02-24 19:52 ` Joost Kremers
2021-02-24 20:08   ` Joost Kremers
2021-02-24 21:08     ` TRS-80 [this message]
2021-02-24 20:57   ` Michael Heerdegen
2021-02-25 16:25   ` Eric S Fraga
2021-02-25 20:40     ` Garjola Dindi
2021-02-24 21:15 ` Stefan Monnier
2021-02-25 16:34   ` Eric S Fraga
2021-02-25 16:51     ` Stefan Monnier
2021-02-26  9:43       ` Eric S Fraga
2021-02-25  0:00 ` [External] : " Drew Adams
2021-02-25  4:28   ` Michael Heerdegen
2021-02-25  7:00     ` Drew Adams
2021-02-25 14:26       ` Stefan Monnier
2021-02-25 16:22         ` Drew Adams
2021-02-25 16:36     ` Eric S Fraga
2021-02-25 16:27   ` Eric S Fraga

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=2196a99d653eab281dc8c3f97ca405cb@isnotmyreal.name \
    --to=lists.trs-80@isnotmyreal.name \
    --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).