[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Keep global-mode-string on its own "modeline"?
From: |
Thuna |
Subject: |
Re: Keep global-mode-string on its own "modeline"? |
Date: |
Sat, 29 Oct 2022 18:41:28 +0200 |
>> Now, I wonder if this could be split off of tab-bar-mode into its own
>> thing.
>
> I am not sure if this is necessary. I don't use tabs, so the tab bar is
> only displaying the global string. If I would use tabs, I don't know if
> having two lines at the top of my screen would be the best usage of
> space. Or am I misunderstanding your point?
No, I was referring splitting the code for displaying the
global-mode-string into its own file.
- Re: Keep global-mode-string on its own "modeline"?, (continued)
- Re: Keep global-mode-string on its own "modeline"?, Thuna, 2022/10/29
- Re: Keep global-mode-string on its own "modeline"?, Eli Zaretskii, 2022/10/29
- Re: Keep global-mode-string on its own "modeline"?, Thuna, 2022/10/29
- Re: Keep global-mode-string on its own "modeline"?, Eli Zaretskii, 2022/10/29
- Re: Keep global-mode-string on its own "modeline"?, Thuna, 2022/10/29
- Re: Keep global-mode-string on its own "modeline"?, John Yates, 2022/10/29
- Re: Keep global-mode-string on its own "modeline"?, Óscar Fuentes, 2022/10/29
Re: Keep global-mode-string on its own "modeline"?, Akib Azmain Turja, 2022/10/29
Re: Keep global-mode-string on its own "modeline"?, Stefan Monnier, 2022/10/29
Re: Keep global-mode-string on its own "modeline"?, Philip Kaludercic, 2022/10/29
- Message not available
- Message not available
- Re: Keep global-mode-string on its own "modeline"?,
Thuna <=
Re: Keep global-mode-string on its own "modeline"?, Visuwesh, 2022/10/29