In <CpOdnbBHrtmv6oDNnZ2dnUVZ_iydnZ2d@giganews.com>
Aaron W. Hsu <arcfide@sacrideo.us> writes:
I have a number of things that I want to do to enhance NN a
bit, foremost among them being Unicode support.
That would be a huge help, and I've been thinking of trying it
myself for a while but have never found the time.
The other item on my wish list is to convert quoted-printable
text to UTF automatically, with an option to force line
wrapping at a user-settable column (because flowed paragraphs
in QP present as a single line with many hundreds of
characters).
On Sat, 8 Jan 2022 20:54:06 -0000 (UTC),
smw <smw@mort.smwonline.ca> wrote:
The other item on my wish list is to convert quoted-printable
text to UTF automatically, with an option to force line
wrapping at a user-settable column (because flowed paragraphs
in QP present as a single line with many hundreds of
characters).
For what it's worth, slrn does this with the command "w" (for
"wrap" I suppose) while reading articles. Maybe knowing what to
look for in that code would simplify using some of it? I could be
way off base here, having only ever glanced at sources.
[added news.software.readers]
On Sat, 8 Jan 2022 20:54:06 -0000 (UTC),
smw <smw@mort.smwonline.ca> wrote:
In <CpOdnbBHrtmv6oDNnZ2dnUVZ_iydnZ2d@giganews.com>
Aaron W. Hsu <arcfide@sacrideo.us> writes:
I have a number of things that I want to do to enhance NN a
bit, foremost among them being Unicode support.
I add my thanks to those of others. I don't use nn myself, but
greatly appreciate the efforts of anyone maintaining programs of
value to the community.
That would be a huge help, and I've been thinking of trying it
myself for a while but have never found the time.
The other item on my wish list is to convert quoted-printable
text to UTF automatically, with an option to force line
wrapping at a user-settable column (because flowed paragraphs
in QP present as a single line with many hundreds of
characters).
For what it's worth, slrn does this with the command "w" (for
"wrap" I suppose) while reading articles. Maybe knowing what to
look for in that code would simplify using some of it? I could be
way off base here, having only ever glanced at sources.
I remember using nn and liking it for it's speed and extensive key bindings. >However, not wrapping long lines would be a deal breaker. Does it really not >have this capability..?
Rockinghorse Winner <Rockinghorse@amgen.com> wrote:
I remember using nn and liking it for it's speed and extensive key bindings. >>However, not wrapping long lines would be a deal breaker. Does it really not >>have this capability..?
Good heavens.
First starting on Usenet in the '90s, my newsreader called the text
editor of my choice for use in the composer. I used the original vi.
Much later, I switched to vim. I had to enter my own line boundary
within paragraphs. It was just like using a typewriter. It was something
I was used to.
Rockinghorse Winner <Rockinghorse@amgen.com> wrote:
I remember using nn and liking it for it's speed and extensive key bindings. >However, not wrapping long lines would be a deal breaker. Does it really not >have this capability..?
Good heavens.
First starting on Usenet in the '90s, my newsreader called the text
editor of my choice for use in the composer. I used the original vi.
Much later, I switched to vim. I had to enter my own line boundary
within paragraphs. It was just like using a typewriter. It was something
I was used to.
If I add text within a line, I have to reformat the paragraph and call a separate paragraph formatter. I usually use fmt but there are others.
Good heavens.
First starting on Usenet in the '90s, my newsreader called the text
editor of my choice for use in the composer. I used the original vi.
Much later, I switched to vim. I had to enter my own line boundary
within paragraphs. It was just like using a typewriter. It was something
I was used to.
If I add text within a line, I have to reformat the paragraph and call a separate paragraph formatter. I usually use fmt but there are others.
The older newsreaders that allow the user to choose is own text editor
and don't provide a built-in text editor are a lot more flexible. I
thought nn didn't provide its own built-in text editor but I really
can't comment.
["Followup-To:" header set to news.software.readers.]
Adam H. Kerman <ahk@chinet.com> wrote:
Good heavens.
First starting on Usenet in the '90s, my newsreader called the text
editor of my choice for use in the composer. I used the original vi.
Much later, I switched to vim. I had to enter my own line boundary
within paragraphs. It was just like using a typewriter. It was something
I was used to.
Some of us still do this, as we have since the 90s (currently on
VIM - Vi IMproved 8.2. Just set your textwidth appropriately in vim,
no problem. You certainly never needed to manually enter carriage
returns "like using a typewriter" if you knew what you were doing.
If I add text within a line, I have to reformat the paragraph and call a >>separate paragraph formatter. I usually use fmt but there are others.
You don't need to go through all that. Just join all lines
(hitting j as required or vipJ to select the whole paragraph in visual
mode, then join it), then gqq. Done.
. . .
Adam H. Kerman <ahk@chinet.com> wrote:
Rockinghorse Winner <Rockinghorse@amgen.com> wrote:
I remember using nn and liking it for it's speed and extensive
key bindings. However, not wrapping long lines would be a deal
breaker. Does it really not have this capability..?
Good heavens.
First starting on Usenet in the '90s, my newsreader called the text
editor of my choice for use in the composer. I used the original vi.
Much later, I switched to vim. I had to enter my own line boundary
within paragraphs. It was just like using a typewriter. It was something
I was used to.
WEll, you do not have to do that in vim, it does line breaks as yu type
just fine.
However, not being able to wrap text in a newsreader is, I think,
obviously talking about READING posts. And not being able to line wrap
posts would make any news reader largely useless or very very
aggravating in 2022.
I even wish I could set a wrap length for slrn other than "window width"
as readable text on a 16:9 laptop screen is only about half the width of
the window.
Lewis <g.kreme@gmail.don-t-email-me.com> wrote:
However, not being able to wrap text in a newsreader is, I think,
obviously talking about READING posts. And not being able to line wrap >>posts would make any news reader largely useless or very very
aggravating in 2022.
My terminal emulation does that, not the newsreader.
Adam H. Kerman <ahk@chinet.com> wrote:
Rockinghorse Winner <Rockinghorse@amgen.com> wrote:
I remember using nn and liking it for it's speed and extensive key bindings.
However, not wrapping long lines would be a deal breaker. Does it really not
have this capability..?
Good heavens.
First starting on Usenet in the '90s, my newsreader called the text
editor of my choice for use in the composer. I used the original vi.
Much later, I switched to vim. I had to enter my own line boundary
within paragraphs. It was just like using a typewriter. It was something
I was used to.
AFAICT, Rockinghorse Winner is talking about wrapping text while
*reading* - not composing - articles. At least he responded to Ted
Heise, who wrote:
[Unsnip:]
<quote>
For what it's worth, slrn does this with the command "w" (for
"wrap" I suppose) while reading articles.
smw <smw@mort.smwonline.ca> wrote:
The other item on my wish list is to convert quoted-printable text to
UTF automatically, with an option to force line wrapping at a
user-settable column (because flowed paragraphs in QP present as a
single line with many hundreds of characters).
For what it's worth, slrn does this with the command "w" (for "wrap" I suppose) while reading articles. Maybe knowing what to look for in
that code would simplify using some of it? I could be way off base
here, having only ever glanced at sources.
Phil Boutros <philb@philb.ca> wrote:
Some of us still do this, as we have since the 90s (currently on
VIM - Vi IMproved 8.2. Just set your textwidth appropriately in vim,
no problem. You certainly never needed to manually enter carriage
returns "like using a typewriter" if you knew what you were doing.
Yeah, I know, but it's not a setting I want turned on much of the time.
On 2022-01-09, Ted Heise <theise@panix.com> wrote:
smw <smw@mort.smwonline.ca> wrote:
The other item on my wish list is to convert quoted-printable text to
UTF automatically, with an option to force line wrapping at a
user-settable column (because flowed paragraphs in QP present as a
single line with many hundreds of characters).
For what it's worth, slrn does this with the command "w" (for "wrap" I
suppose) while reading articles. Maybe knowing what to look for in
that code would simplify using some of it? I could be way off base
here, having only ever glanced at sources.
slrn's pager wraps (if wrapping is desired) at the edge of the screen or window, not at "a user-settable column". I'm not sure why a user would
want to set a column for wrapping.
Other aspects of wrapping are configurable in slrn by setting the
variables "wrap_flags" and "wrap_method" in .slrnrc.
https://slrn.info/docs/slrn-manual-6.html#ss6.133 https://slrn.info/docs/slrn-manual-6.html#ss6.134
slrn is written in C. If nn is written is C, the relevant code ought to
be easy to adapt.
https://slrn.info/download.html
In message <slrnsu3kjm.278s.pjr@pjr.example.invalid> Peter J Ross <pjr@example.invalid> wrote:
On 2022-01-09, Ted Heise <theise@panix.com> wrote:
smw <smw@mort.smwonline.ca> wrote:
The other item on my wish list is to convert quoted-printable text to
UTF automatically, with an option to force line wrapping at a
user-settable column (because flowed paragraphs in QP present as a
single line with many hundreds of characters).
For what it's worth, slrn does this with the command "w" (for "wrap" I
suppose) while reading articles. Maybe knowing what to look for in
that code would simplify using some of it? I could be way off base
here, having only ever glanced at sources.
slrn's pager wraps (if wrapping is desired) at the edge of the screen or
window, not at "a user-settable column". I'm not sure why a user would
want to set a column for wrapping.
Because the appropriate width for a terminal that is used for terminal
stuff like looking at code or logs is too wide for reading news, so it
would be much better if slrn supported a reasonable line wrap length the
user could set rather that constraining only to the width of the screen
or window.
Other aspects of wrapping are configurable in slrn by setting the
variables "wrap_flags" and "wrap_method" in .slrnrc.
https://slrn.info/docs/slrn-manual-6.html#ss6.133
https://slrn.info/docs/slrn-manual-6.html#ss6.134
Neither of those cover this.
slrn is written in C. If nn is written is C, the relevant code ought to
be easy to adapt.
Isn't slrn written in SLANG?
["Followup-To:" header set to news.software.readers.]
johnson <root@example.net> wrote:
["Followup-To:" header set to news.software.readers.]
Here's the way it works: If YOU think thread drift has rendered it off
topic in one or more newsgroups in the crosspost, then YOU cut the
crosspost.
You just posted off topic. Setting Followup-To is a case of Do As I Say, Don't Do As I Do.
No one posting a followup has to follow your instructions in
Followup-To. The author is responsible for whether he crossposts, not
the author of the precursor article.
On 2022-01-09, Ted Heise <theise@panix.com> wrote:
smw <smw@mort.smwonline.ca> wrote:
The other item on my wish list is to convert quoted-printable text to
UTF automatically, with an option to force line wrapping at a
user-settable column (because flowed paragraphs in QP present as a
single line with many hundreds of characters).
For what it's worth, slrn does this with the command "w" (for "wrap" I suppose) while reading articles. Maybe knowing what to look for in
that code would simplify using some of it? I could be way off base
here, having only ever glanced at sources.
slrn's pager wraps (if wrapping is desired) at the edge of the screen or window, not at "a user-settable column". I'm not sure why a user would
want to set a column for wrapping.
Peter J Ross <pjr@example.invalid> wrote:
On 2022-01-09, Ted Heise <theise@panix.com> wrote:
smw <smw@mort.smwonline.ca> wrote:
The other item on my wish list is to convert
quoted-printable text to UTF automatically, with an option
to force line wrapping at a user-settable column (because
flowed paragraphs in QP present as a single line with many
hundreds of characters).
For what it's worth, slrn does this with the command "w"
(for "wrap" I suppose) while reading articles. Maybe
knowing what to look for in that code would simplify using
some of it? I could be way off base here, having only ever
glanced at sources.
slrn's pager wraps (if wrapping is desired) at the edge of the
screen or window, not at "a user-settable column". I'm not
sure why a user would want to set a column for wrapping.
Does slrn do *word*-wrapping or just 'character'-wrapping,
i.e. 'folding' the line at the end of the window?
My newsreader is tin and its pager (at least the one in this
very old version) does not wrap long lines. But my 'terminal'
(actually a (Windows) 'Command Prompt' window) does
'character'-wrapping at the edge of the window. I would like if
the tin pager could do word-wrapping.
johnson <root@example.net> wrote:
["Followup-To:" header set to news.software.readers.]
Here's the way it works: If YOU think thread drift has rendered it off
topic in one or more newsgroups in the crosspost, then YOU cut the
crosspost.
You just posted off topic. Setting Followup-To is a case of Do As I Say, Don't Do As I Do.
No one posting a followup has to follow your instructions in
Followup-To. The author is responsible for whether he crossposts, not
the author of the precursor article.
In message <slrnsu3kjm.278s.pjr@pjr.example.invalid> Peter J Ross <pjr@example.invalid> wrote:
On 2022-01-09, Ted Heise <theise@panix.com> wrote:
smw <smw@mort.smwonline.ca> wrote:
The other item on my wish list is to convert quoted-printable text to
UTF automatically, with an option to force line wrapping at a
user-settable column (because flowed paragraphs in QP present as a
single line with many hundreds of characters).
For what it's worth, slrn does this with the command "w" (for "wrap" I
suppose) while reading articles. Maybe knowing what to look for in
that code would simplify using some of it? I could be way off base
here, having only ever glanced at sources.
slrn's pager wraps (if wrapping is desired) at the edge of the screen or
window, not at "a user-settable column". I'm not sure why a user would
want to set a column for wrapping.
Because the appropriate width for a terminal that is used for terminal
stuff like looking at code or logs is too wide for reading news, so it
would be much better if slrn supported a reasonable line wrap length the
user could set rather that constraining only to the width of the screen
or window.
Other aspects of wrapping are configurable in slrn by setting the
variables "wrap_flags" and "wrap_method" in .slrnrc.
https://slrn.info/docs/slrn-manual-6.html#ss6.133
https://slrn.info/docs/slrn-manual-6.html#ss6.134
Neither of those cover this.
slrn is written in C. If nn is written is C, the relevant code ought to
be easy to adapt.
Isn't slrn written in SLANG?
https://slrn.info/download.html
Peter J Ross <pjr@example.invalid> wrote:
On 2022-01-09, Ted Heise <theise@panix.com> wrote:
smw <smw@mort.smwonline.ca> wrote:
The other item on my wish list is to convert quoted-printable text to
UTF automatically, with an option to force line wrapping at a
user-settable column (because flowed paragraphs in QP present as a
single line with many hundreds of characters).
For what it's worth, slrn does this with the command "w" (for "wrap" I
suppose) while reading articles. Maybe knowing what to look for in
that code would simplify using some of it? I could be way off base
here, having only ever glanced at sources.
slrn's pager wraps (if wrapping is desired) at the edge of the screen or
window, not at "a user-settable column". I'm not sure why a user would
want to set a column for wrapping.
Does slrn do *word*-wrapping or just 'character'-wrapping, i.e.
'folding' the line at the end of the window?
My newsreader is tin and its pager (at least the one in this very old version) does not wrap long lines. But my 'terminal' (actually a
(Windows) 'Command Prompt' window) does 'character'-wrapping at the edge
of the window. I would like if the tin pager could do word-wrapping.
Peter J Ross <pjr@example.invalid> wrote:
On 2022-01-09, Ted Heise <theise@panix.com> wrote:
smw <smw@mort.smwonline.ca> wrote:
The other item on my wish list is to convert quoted-printable text to
UTF automatically, with an option to force line wrapping at a
user-settable column (because flowed paragraphs in QP present as a
single line with many hundreds of characters).
For what it's worth, slrn does this with the command "w" (for "wrap" I
suppose) while reading articles. Maybe knowing what to look for in
that code would simplify using some of it? I could be way off base
here, having only ever glanced at sources.
slrn's pager wraps (if wrapping is desired) at the edge of the screen or
window, not at "a user-settable column". I'm not sure why a user would
want to set a column for wrapping.
Does slrn do *word*-wrapping or just 'character'-wrapping, i.e.
'folding' the line at the end of the window?
On 2022-01-15, Adam H. Kerman <ahk@chinet.com> wrote:
johnson <root@example.net> wrote:
["Followup-To:" header set to news.software.readers.]
Here's the way it works: If YOU think thread drift has rendered it off topic in one or more newsgroups in the crosspost, then YOU cut the crosspost.
You just posted off topic. Setting Followup-To is a case of Do As I Say, Don't Do As I Do.
No one posting a followup has to follow your instructions in
Followup-To. The author is responsible for whether he crossposts, not
the author of the precursor article.
The "Followup-To:" line is advisory and tentative. johnson has observed proper netiquette by including a mention of it in the body of his post.
On 2022-01-15, Frank Slootweg <this@ddress.is.invalid> wrote:
My newsreader is tin and its pager (at least the one in this very old version) does not wrap long lines. But my 'terminal' (actually a
(Windows) 'Command Prompt' window) does 'character'-wrapping at the edge
of the window. I would like if the tin pager could do word-wrapping.
Why not submit a feature request to the tin developers? Of course,
you'll need to check that later versions of tin don't already include
the feature.
OT: It's good to see that you're alive and (I hope) well, Frank. It must
be at least 15 years since we first debated the relative merits of our preferred newsreaders.
My newsreader is tin and its pager (at least the one in this very old version) does not wrap long lines. But my 'terminal' (actually a
(Windows) 'Command Prompt' window) does 'character'-wrapping at the edge
of the window. I would like if the tin pager could do word-wrapping.
In news.software.readers Frank Slootweg <this@ddress.is.invalid> wrote:
My newsreader is tin and its pager (at least the one in this very old
version) does not wrap long lines. But my 'terminal' (actually a
(Windows) 'Command Prompt' window) does 'character'-wrapping at the edge
of the window. I would like if the tin pager could do word-wrapping.
Hard to say what you mean by "very old version" but doesn't control-T (while in post mode) bring up something like this?
T Overtype OFF I Autoindent OFF Word wrap OFF
D Tab width 8 Left margin 1 Right margin 77
X Rectangle mode OFF Case insensitivity OFF Search wraps OFF
Menu explorer ON Autoswap mode OFF Indent char 32
Indent step 2 french spacing OFF Highlighting ON
no tabs OFF Center on scroll OFF Auto detect CR-LF ON
Guess indent ON Z CR-LF (MS-DOS) OFF N Line numbers OFF
Marking OFF Meta chars as-is OFF Force last NL OFF
Disable backups OFF Auto unmark OFF Exit ask OFF
The word wrap is 3rd column, first row. Never did figure out how to default it to ON.
In news.software.readers Frank Slootweg <this@ddress.is.invalid> wrote:
My newsreader is tin and its pager (at least the one in this very old version) does not wrap long lines. But my 'terminal' (actually a
(Windows) 'Command Prompt' window) does 'character'-wrapping at the edge
of the window. I would like if the tin pager could do word-wrapping.
Hard to say what you mean by "very old version" but doesn't control-T (while in post mode) bring up something like this?
T Overtype OFF I Autoindent OFF Word wrap OFF
D Tab width 8 Left margin 1 Right margin 77
X Rectangle mode OFF Case insensitivity OFF Search wraps OFF
Menu explorer ON Autoswap mode OFF Indent char 32
Indent step 2 french spacing OFF Highlighting ON
no tabs OFF Center on scroll OFF Auto detect CR-LF ON
Guess indent ON Z CR-LF (MS-DOS) OFF N Line numbers OFF Marking OFF Meta chars as-is OFF Force last NL OFF
Disable backups OFF Auto unmark OFF Exit ask OFF
The word wrap is 3rd column, first row. Never did figure out how to default it to ON.
[Crosspost reduced, because this has nothing to do with Slackware]
Sorry, but the subject is about (word) wrapping text while *reading* -
not composing/editing - articles. See my reference to the "pager", i.e. output, not input.
Sysop: | Keyop |
---|---|
Location: | Huddersfield, West Yorkshire, UK |
Users: | 285 |
Nodes: | 16 (2 / 14) |
Uptime: | 70:35:15 |
Calls: | 6,488 |
Calls today: | 1 |
Files: | 12,096 |
Messages: | 5,275,488 |