From: Glenn Morris <rgm@gnu.org>
To: Raimon Grau <raimonster@gmail.com>
Cc: 13073@debbugs.gnu.org
Subject: bug#13073: 24.0.91; (window-width) doesn't take into account text-scale-adjust 'ed buffers
Date: Mon, 03 Dec 2012 21:21:30 -0500 [thread overview]
Message-ID: <da4nk2y2tx.fsf@fencepost.gnu.org> (raw)
In-Reply-To: <87k3syob4p.fsf@gmail.com> (Raimon Grau's message of "Tue, 04 Dec 2012 02:32:22 +0100")
Raimon Grau wrote:
> I'm trying to get the maximum number of chars that a line would accept
> without overflowing of wrapping
>
> (window-width) gives the number of columns of a given window, but if I
> increase the size of the font, window-width doesn't change the
> value returned.
Please see
http://debbugs.gnu.org/cgi/bugreport.cgi?bug=9949
prev parent reply other threads:[~2012-12-04 2:21 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-04 1:32 bug#13073: 24.0.91; (window-width) doesn't take into account text-scale-adjust 'ed buffers Raimon Grau
2012-12-04 2:21 ` Glenn Morris [this message]
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=da4nk2y2tx.fsf@fencepost.gnu.org \
--to=rgm@gnu.org \
--cc=13073@debbugs.gnu.org \
--cc=raimonster@gmail.com \
/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 public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).