[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Documenting buffer display
From: |
Eli Zaretskii |
Subject: |
Re: Documenting buffer display |
Date: |
Wed, 24 Oct 2018 21:25:31 +0300 |
> Date: Wed, 24 Oct 2018 19:40:02 +0200
> From: martin rudalics <address@hidden>
> CC: address@hidden
>
> But once an application directly or indirectly calls 'display-buffer'
> the latter's customizations may kick in and invalidate all assumptions
> about the window used. So if your NO-SELECT or Juri's directional
> effort fail, 'display-buffer' will inevitably rule the game.
As I said before, this is okay, IMO, if used only rarely and not
promoted as the main or even just important way of tweaking what
commands do.
- Re: Documenting buffer display, (continued)
- Re: Documenting buffer display, Eli Zaretskii, 2018/10/23
- Re: Documenting buffer display, martin rudalics, 2018/10/23
- Re: Documenting buffer display, Eli Zaretskii, 2018/10/23
- Re: Documenting buffer display, martin rudalics, 2018/10/24
- Re: Documenting buffer display, Eli Zaretskii, 2018/10/24
- Re: Documenting buffer display, martin rudalics, 2018/10/24
- Re: Documenting buffer display,
Eli Zaretskii <=
- Re: Documenting buffer display, Juri Linkov, 2018/10/25
- Re: Documenting buffer display, Alan Mackenzie, 2018/10/23
- Re: Documenting buffer display, martin rudalics, 2018/10/23
Re: Documenting buffer display, Michael Welsh Duggan, 2018/10/21
RE: Documenting buffer display, Drew Adams, 2018/10/20