[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Documenting buffer display
From: |
martin rudalics |
Subject: |
Re: Documenting buffer display |
Date: |
Sat, 20 Oct 2018 20:02:47 +0200 |
> Being able to simply bind an option such as `pop-up-frames',
> to change the behavior of existing code, is very useful.
If it overrides a user's customization then that's not useful but bad.
> Please keep supporting, and not at all discourage, `pop-up-frames'
> and similar.
We do our best to support them in present code. We have to discourage
their use because there's no guarantee that future code will support
them.
Have you read what I wrote about 'pop-up-frame-alist'? Already now
there's no guarantee that we can maintain these old options properly.
And I never tried to probe very deep in this area.
martin
- Re: Documenting buffer display, (continued)
- 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, 2018/10/24
- 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
- Re: Documenting buffer display,
martin rudalics <=