Reply to topic

Size of EchoArea of Emacsclient

zariski
Registered Member
Posts
7
Karma
0

Size of EchoArea of Emacsclient

Thu Jan 09, 2014 11:36 pm
I am facing a strange problem. After I change the KDE window rules for emacsclient24 according to http://www.emacswiki.org/emacs/KdeMaximized, that is, I created a special window setting:
Image


the size of echoarea (the area shared with minibuffer) is doubled by default whenever the font size is larger than 115 (1/10 pt):

Image

while normally it should be like this:

Image

**Moreover, this only occurs when emacsclient is maximized and without menubar (it is fine when fullscreened or not maximized or with menubar).**

Surely a workaround is to set font size to be at most 115, but that looks too small on my 13.3 ultrabook and I usually set it to 125.

So I am just wondering how to resolve this?

I am using emacs 24.3.

Thanks!
luebking
Registered Member
Posts
923
Karma
7
You don't.

Emacs wants to grow by multiples of the fonts size. The rule allows kwin to grow it by arbitry sizes, but emacs can't make any reasonable use of the leftover size and just puts it to the end of the window.
It looks like you're near the next size, so if it had just a little more space (smaller titlebar or panel?) it could provide you another row in the editor instead of "wasting" the space in the minibuffer.

If you've a recent KDE version and just want to prevent emacs from resizing itself when it feels like it got the wrong size, use "ignore requested geometry" and set it to "force" (not apply initally - if it does not have latter, force meant sth. different and you KDE version is too old for this)
This will prevent emacs from resizing itself no matter whether it's maximized or not and (without the other rule) still grow in multiples of a row - leaving a small area where it shows the desktop on top and/or bottom (you can still move the maximized window to align to a border)
zariski
Registered Member
Posts
7
Karma
0

Re: Size of EchoArea of Emacsclient

Fri Jan 10, 2014 4:17 am
Thanks! But preventing "leaving a small area that shows the desktop" is why I created the special window rules in the first place... hmm, I guess I just have to get used to it.

luebking wrote:You don't.

Emacs wants to grow by multiples of the fonts size. The rule allows kwin to grow it by arbitry sizes, but emacs can't make any reasonable use of the leftover size and just puts it to the end of the window.
It looks like you're near the next size, so if it had just a little more space (smaller titlebar or panel?) it could provide you another row in the editor instead of "wasting" the space in the minibuffer.

If you've a recent KDE version and just want to prevent emacs from resizing itself when it feels like it got the wrong size, use "ignore requested geometry" and set it to "force" (not apply initally - if it does not have latter, force meant sth. different and you KDE version is too old for this)
This will prevent emacs from resizing itself no matter whether it's maximized or not and (without the other rule) still grow in multiples of a row - leaving a small area where it shows the desktop on top and/or bottom (you can still move the maximized window to align to a border)
zariski
Registered Member
Posts
7
Karma
0

Re: Size of EchoArea of Emacsclient

Sat Jan 11, 2014 11:47 pm
So actually one way is to test all font sizes that may fit. I mentioned in the thread that any font size above 11.5pt would not work, but in fact although 12pt,12.5pt and 13pt all give "enlarged" echoarea, 13.5pt gives a normal size echoarea. And 13.5pt is actually not too "larger" than 12.5pt which I preferred since with 13.5pt emacs does not have to "waste" those unused echoarea (on my screen, 12.5pt gives 40 lines of codes, and 13.5pt gives 39 lines of codes).

 
Reply to topic

Bookmarks



Who is online

Registered users: Alexa [Bot], asevens, Baidu [Spider], Bing [Bot], binro, brand, doublerainbow64, Exabot [Bot], Google [Bot], google01103, inksi, jgrulich, koriun, lazyit, Majestic-12 [Bot], metzman, MSNbot Media, Murz, random_fan, rfinley, Sentynel, toad, Vindex17, whatthefunk, Yahoo [Bot], yurchor, zhou13