9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Uriel <lost.goblin@gmail.com>
To: 9fans <9fans@cse.psu.edu>
Subject: [9fans] Re: line wrapping
Date: Tue,  7 Feb 2006 10:02:46 +0100	[thread overview]
Message-ID: <5d375e920602070102x2278ffbcyff7125c1e146c43@mail.gmail.com> (raw)
In-Reply-To: <20060202063702.D68D91E8C24@holo.morphisms.net>

On 2/2/06, Russ Cox <rsc@swtch.com> wrote:
>
> uriel rsc9: is there any reason for the wraping of lines
>           at 80 chars in wikifs?  why not let acme wrap lines
>           to whatever the window size is?  (I have seen this also
>           in irc7, and I still don't understand why, to me it
>           seems like an annoying misfeature, but I guess there
>           has to be a reason for it)
>
> acme line wrapping is a last resort.
> it wraps mid-word and looks ugly.
Maybe acme should know how to do word-wrapping? Or is there a reason for it not
to?

Acme is already word-aware for double-click selection, so it's not so
much of a philosophical breach; only problem I see is that it might
make hard
to know if the line break is in the file or inserted by acme, but that
problem already exists, any ideas about how to mark line wrapping?

I have seen quite a few apps that do word warping on their own just
because they are intended to run inside acme , and usually with less
than ideal results(eg., irc7)

uriel

>
> it is true that Wiki itself should
> be doing the line wrapping, but unless
> you want to write that code, i would
> just leave the wrapping in wikifs.
>
>

       reply	other threads:[~2006-02-07  9:02 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20060202063702.D68D91E8C24@holo.morphisms.net>
2006-02-07  9:02 ` Uriel [this message]
2006-02-07  9:41   ` Russ Cox
2006-02-07  9:55     ` uriel

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=5d375e920602070102x2278ffbcyff7125c1e146c43@mail.gmail.com \
    --to=lost.goblin@gmail.com \
    --cc=9fans@cse.psu.edu \
    /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).