bug-gnu-emacs
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

bug#43572: Feature request: make it possible to choose whether the first


From: Gregory Heytings
Subject: bug#43572: Feature request: make it possible to choose whether the first lines of the minibuffer should be displayed instead of the last ones
Date: Wed, 23 Sep 2020 22:47:05 +0000
User-agent: Alpine 2.22 (NEB 394 2020-01-19)



Really?  Despite the `-Q`?  Is it using a proportional font?
Oh, wait, is it because you're running that Emacs session in a tty rather than 
in a GUI?


Yes, yes, no, no ;-)


How many columns wide is the frame?


167, Sir! ;-)

No, if you look at the patch its value is reset to nil whenever the minibuffer is entered.

That still leaves the non-minibuffer uses of the mini window (i.e. the echo area).

And of course, that will also result in the use of an incorrect value when you exit a *nested* minibuffer (unless both minibuffers were using the same value).


Thank you very much for the pointers, indeed I completely forgot about these cases. See the attached corrected patch, in which they are dealt with. I believe start_display_at_beginning_of_minibuffer how has the value it should have whenever resize_mini_window() is called.

I don't have a patch to suggest, but I think ideally, I'd want clients like icomplete to tell the redisplay either something like "please display as much as possible of *this* chunk of text" or maybe "feel free not to display all of this overlay, it's not super important".

Yes, that's the point. The patch I proposed tells redisplay "please display as much as possible of the text between BOB and point", when the current behavior tells redisplay "please display as much as possible of the text between point and EOB". Something more fine-grained would of course be possible, but I don't think it is a good idea to implement a feature when there is no clear need for it.

I think what I was getting at is that this "request" should come from the minibuffer's text rather than from a variable.


If this were possible, it would be even better indeed. An "importance" text property, which would inform redisplay (?) of the relative importance of the parts of the buffer. But implementing this is several orders of magnitude harder than implementing my proposal.

Attachment: start-display-at-beginning-of-minibuffer.patch
Description: Text Data


reply via email to

[Prev in Thread] Current Thread [Next in Thread]