From: David Reitter <david.reitter@gmail.com>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: Emacs-Devel devel <emacs-devel@gnu.org>
Subject: Re: completion buffer - unsuitable column width
Date: Tue, 3 Mar 2009 10:47:56 -0500 [thread overview]
Message-ID: <5B840E04-FA6D-410A-B2F8-F1D24DAB4A4D@gmail.com> (raw)
In-Reply-To: <jwvk5767kqp.fsf-monnier+emacs@gnu.org>
[-- Attachment #1: Type: text/plain, Size: 1060 bytes --]
On 3 Mar 2009, at 09:21, Stefan Monnier wrote:
>> A grep over the source, looking for (window-width), reveals other
>> suspicious uses.
>
> No doubt. This is just another instance of the long standing problem
> that all/most of the code presumes fixed-width fonts (and of a single
> width shared by all fonts) as was the case in Emacs<21.
I suspect that most developers here use a single mono-spaced font for
most or all their editing... I started running the NS port of 23 for
some regular editing now, and I've run into a number of bugs.
>> "window-buffer-width", giving the average (expected) number of
>> columns in
>> a window for text in the default face applicable to the buffer
>> shown in
>> a given window.
>
> Yes, that could help.
OK, what is the plan regarding this for 23.1? Do nothing, add a
fairly safe workaround as I suggested, or try to implement window-
buffer-width?
I don't think I can help implementing window-buffer-width in the
available time; it takes someone who knows the (re)display code fairly
well I think.
[-- Attachment #2: smime.p7s --]
[-- Type: application/pkcs7-signature, Size: 2193 bytes --]
next prev parent reply other threads:[~2009-03-03 15:47 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-02 19:13 completion buffer - unsuitable column width David Reitter
2009-03-03 1:33 ` Stefan Monnier
2009-03-03 13:23 ` David Reitter
2009-03-03 14:21 ` Stefan Monnier
2009-03-03 15:47 ` David Reitter [this message]
2009-03-03 18:03 ` Stefan Monnier
2009-03-03 16:46 ` Dan Nicolaescu
2009-03-03 16:33 ` Jonathan Rockway
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=5B840E04-FA6D-410A-B2F8-F1D24DAB4A4D@gmail.com \
--to=david.reitter@gmail.com \
--cc=emacs-devel@gnu.org \
--cc=monnier@iro.umontreal.ca \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.