all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Lennart Borgman <lennart.borgman@gmail.com>
To: Chong Yidong <cyd@gnu.org>
Cc: Ivan Andrus <darthandrus@gmail.com>, 11759@debbugs.gnu.org
Subject: bug#11759: 24.1.50; word-wrap should wrap on non-words if the current word is too long
Date: Sat, 23 Jun 2012 13:27:20 +0200	[thread overview]
Message-ID: <CANbX365aOceonNERReTS=Hd16LP29x7PYnxgRzOmdkfVQ9-5bw@mail.gmail.com> (raw)
In-Reply-To: <87vcii701n.fsf@gnu.org>

On Sat, Jun 23, 2012 at 1:14 PM, Chong Yidong <cyd@gnu.org> wrote:
> Stefan Monnier <monnier@IRO.UMontreal.CA> writes:
>
>>> if the entire line is one "word" but indented, which is not uncommon
>>> in some files that I regularly edit, then the entire line is wrapped
>>> to the next line leaving a completely blank visual line.
>>
>> I also use word-wrap everywhere, including programming modes and see the
>> same problem.
>>
>> - if the word is the first non-blank char on the line, wrapping to the
>>   next line results in a visually empty line, losing the
>>   indentation info.
>> - if the word is wider than the window (plus the wrap-prefix), then even
>>   after word-wrapping it to the next line, it gets char-wrapped anyway,
>>   so we didn't win anything.
>
> FWIW, word wrap behaves the same way in other editors (checked with
> gedit and with a text box in Firefox).

I think it will be very nice if such long words could wrap. It would
also be nice to have the alternative to truncate such long words.
(They are often URL in my case and truncating them with the full URL
as a help string would be fine.)





  reply	other threads:[~2012-06-23 11:27 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-06-21 16:27 bug#11759: 24.1.50; word-wrap should wrap on non-words if the current word is too long Ivan Andrus
2012-06-21 17:09 ` Stefan Monnier
2012-06-23 11:14   ` Chong Yidong
2012-06-23 11:27     ` Lennart Borgman [this message]
2012-06-23 12:48       ` Eli Zaretskii
2012-06-23 13:06         ` Lennart Borgman
2012-06-23 15:15     ` Stefan Monnier

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='CANbX365aOceonNERReTS=Hd16LP29x7PYnxgRzOmdkfVQ9-5bw@mail.gmail.com' \
    --to=lennart.borgman@gmail.com \
    --cc=11759@debbugs.gnu.org \
    --cc=cyd@gnu.org \
    --cc=darthandrus@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 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.