Gnus development mailing list
 help / color / mirror / Atom feed
From: Jesper Harder <harder@ifa.au.dk>
Subject: Re: gnus-correct-length vs. string-width
Date: Sun, 30 Dec 2001 02:32:38 +0100	[thread overview]
Message-ID: <m3heq9ebm1.fsf@defun.localdomain> (raw)
In-Reply-To: <iluadw3mf85.fsf@extundo.com> (jas@extundo.com's message of "Fri, 28 Dec 2001 17:29:24 +0000 (UTC)")

jas@extundo.com (Simon Josefsson) writes:

> Jesper Harder <harder@ifa.au.dk> writes:
>
>> Is the built-in function `string-width' known to be broken?
>
> When I try the examples from the original thread
> (<87itf461hj.fsf@inanna.rimspace.net> etc) 

Thanks for the pointer.  I hadn't noticed that it is customizable with
`gnus-use-correct-string-widths'.  So it's not so bad after all, though
I think nil would maybe be a better default, because it is so slow.

But there still seems to be a bug in the code in
`gnus-parse-simple-format'.  If I set `gnus-use-correct-string-widths'
to nil, `gnus-correct-length' is still used, although less frequently
than before.

Hmm, I don't really understand the code, but AFAICS the problem is the
condition in line 558 (gnus-spec.el):

	  (if (or max-width cut-width ignore-value
		  (and (featurep 'xemacs)
		       gnus-use-correct-string-widths))

which causes `gnus-correct-pad-form' to be used even if
g-u-c-string-widths is nil.




      parent reply	other threads:[~2001-12-30  1:32 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-12-28 14:26 Jesper Harder
2001-12-28 17:22 ` Simon Josefsson
2001-12-28 23:24   ` Lars Magne Ingebrigtsen
2002-01-05  7:00     ` Daniel Pittman
2002-01-05 16:08       ` Lars Magne Ingebrigtsen
2002-01-06 11:25         ` Daniel Pittman
2001-12-30  1:32   ` Jesper Harder [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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=m3heq9ebm1.fsf@defun.localdomain \
    --to=harder@ifa.au.dk \
    /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. 
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 NNTP newsgroup(s).