• nn (was: Replace Google Groups with ?)

    From Ted Heise@21:1/5 to smw on Sun Jan 9 13:22:22 2022
    XPost: alt.os.linux.slackware

    [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.

    --
    Ted Heise <theise@panix.com> West Lafayette, IN, USA

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From smw@21:1/5 to Ted Heise on Mon Jan 10 00:06:27 2022
    XPost: alt.os.linux.slackware

    In <slrnstloce.cir.theise@panix2.panix.com>
    Ted Heise <theise@panix.com> writes:

    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.

    Thank you! That does help.

    - Steven
    --
    ___________________________________________________________________________ Steven Winikoff |
    Montreal, QC, Canada | "Ninety percent of most magic merely
    smw@smwonline.ca | consists of knowing one extra fact." http://smwonline.ca |
    | - Terry Pratchett

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Rockinghorse Winner@21:1/5 to Ted Heise on Thu Jan 13 12:52:01 2022
    XPost: alt.os.linux.slackware

    On 2022-01-09, Ted Heise <theise@panix.com> wrote:

    [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..?

    --

    "Many have sought in vain to tell joyously of the Most Joyous. Now at last It declares Itself to me, now in this misery." - Holderlin

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Adam H. Kerman@21:1/5 to Rockinghorse Winner on Thu Jan 13 14:37:59 2022
    XPost: alt.os.linux.slackware

    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.

    I personally do not care for a composer acting like a word processor in
    which paragraphs are reformatted on the fly and especially if soft line
    breaks are used, which aren't ASCII characters and must not be sent to
    Usenet.

    If I'm writing a document that has to look neat and not a quick followup
    on Usenet, then I'll use a text editor outside of the newsreader, make
    sure it's output as pure ASCII with a fixed-width font and proper line
    length, then read that file into the composer when I'm ready to prepare
    the article for injection into Usenet.

    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.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Lewis@21:1/5 to Adam H. Kerman on Thu Jan 13 15:20:03 2022
    XPost: alt.os.linux.slackware

    In message <srpdg7$hav$1@dont-email.me> 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.

    --
    Once upon a time the plural of 'wizard' was 'war'. --The Last
    Continent

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Frank Slootweg@21:1/5 to Adam H. Kerman on Thu Jan 13 15:52:01 2022
    XPost: alt.os.linux.slackware

    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.

    </quote>

    See also Lewis' response talking about wrapping while reading
    articles.

    FWIW, I also would like my newsreader - tin - to wrap too long lines
    while reading articles, but AFAIK it's pager is fixed/built-in. But as a
    use a very old version, I may be wrong.

    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.

    As Lewis mentions, vim can wrap during composing and vim can rewrap a paragraph after editing it, but using fmt is of course perfectly fine.
    I was doing that when I still had vi, not vim.

    ['+1' comments deleted]

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Phil Boutros@21:1/5 to Adam H. Kerman on Thu Jan 13 16:56:36 2022
    XPost: alt.os.linux.slackware

    ["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.

    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.

    Which is inconsequential to the discussion of nn, as I believe the
    person was talking about wrapping lines while *reading*. As others
    have mentioned, hitting 'w' in slrn does this nicely for those who are
    deprived of a properly formatting editor and newsreader (which should
    be nice enough to warn you if you are attempting to post with lines
    that are too long. Too bad the GNKSA is dead. I believe that was one
    of the "shoulds". It's not a feature that I use often, but invaluable
    when I do.


    Phil
    --
    AH#61 Wolf#14 BS#89 bus#1 CCB#1 SENS KOTC#4
    philb@philb.ca http://philb.ca

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Adam H. Kerman@21:1/5 to Phil Boutros on Thu Jan 13 18:24:38 2022
    XPost: alt.os.linux.slackware

    Phil Boutros <philb@philb.ca> wrote:

    ["Followup-To:" header set to news.software.readers.]

    I'm retaining the crosspost.

    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.

    Yeah, I know, but it's not a setting I want turned on much of the time.

    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.

    That's multiple commands! !fmt -76 (or whatever line length)

    . . .

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Adam H. Kerman@21:1/5 to Lewis on Thu Jan 13 18:18:24 2022
    XPost: alt.os.linux.slackware

    Lewis <g.kreme@gmail.don-t-email-me.com> wrote:
    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.

    Eh. That command got turned on automatically in some linux update and
    I'm not sure which one it is. I haven't looked for it in the help text.
    Much of the time, I'd prefer not to have the automatic line break
    because I still have to reformat the paragraph.

    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.

    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.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Lewis@21:1/5 to Adam H. Kerman on Thu Jan 13 20:58:39 2022
    XPost: alt.os.linux.slackware

    In message <srpqdg$a55$3@dont-email.me> Adam H. Kerman <ahk@chinet.com> wrote:
    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.

    Ah, but normally in the terminal long lines are great, because reading
    and editing source ode short line lengths quickly march off the right
    side, while a newsreader does not have that issue.


    --
    Major Strasser has been shot. Round up the usual suspects.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Rockinghorse Winner@21:1/5 to Frank Slootweg on Fri Jan 14 01:12:20 2022
    XPost: alt.os.linux.slackware

    On 2022-01-13, Frank Slootweg <this@ddress.is.invalid> wrote:
    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.

    Yes, about 1/8 of the articles I read use extra long line lengths. On slrn, this is a snap. But having to use the arrow keys to navigate this mess is a
    non starter for me. :)


    --

    "Many have sought in vain to tell joyously of the Most Joyous. Now at last It declares Itself to me, now in this misery." - Holderlin

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Peter J Ross@21:1/5 to Ted Heise on Fri Jan 14 19:43:50 2022
    XPost: alt.os.linux.slackware

    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


    --
    PJR :-)

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Peter J Ross@21:1/5 to Adam H. Kerman on Fri Jan 14 19:21:16 2022
    XPost: alt.os.linux.slackware

    On 2022-01-13, Adam H. Kerman <ahk@chinet.com> wrote:
    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.

    :set tw=0


    --
    PJR :-)

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Lewis@21:1/5 to Peter J Ross on Sat Jan 15 00:44:57 2022
    XPost: alt.os.linux.slackware

    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




    --
    No man is free who is not master of himself

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From johnson@21:1/5 to Lewis on Sat Jan 15 05:05:49 2022
    XPost: alt.os.linux.slackware

    ["Followup-To:" header set to news.software.readers.]
    On 2022-01-15, Lewis <g.kreme@kreme.dont-email.me> wrote:
    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?


    no, slrn is written in C (as also is slang)

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Adam H. Kerman@21:1/5 to johnson on Sat Jan 15 05:23:33 2022
    XPost: alt.os.linux.slackware

    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.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From David Robley@21:1/5 to Adam H. Kerman on Sat Jan 15 19:18:09 2022
    On 15/1/22 3:53 pm, Adam H. Kerman 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.

    Maybe this will stop static in aols

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Frank Slootweg@21:1/5 to Peter J Ross on Sat Jan 15 13:20:47 2022
    XPost: alt.os.linux.slackware

    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.

    [...]

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Ted Heise@21:1/5 to Frank Slootweg on Sat Jan 15 15:02:27 2022
    XPost: alt.os.linux.slackware

    On 15 Jan 2022 13:20:47 GMT,
    Frank Slootweg <this@ddress.is.invalid> wrote:
    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.

    The w command in slrn article reading mode wraps text by word.

    --
    Ted Heise <theise@panix.com> West Lafayette, IN, USA

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Peter J Ross@21:1/5 to Adam H. Kerman on Sat Jan 15 18:44:00 2022
    XPost: alt.os.linux.slackware

    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.

    I'm not sure why you're complaining about good behaviour.


    --
    PJR :-)

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Peter J Ross@21:1/5 to Lewis on Sat Jan 15 18:30:40 2022
    XPost: alt.os.linux.slackware

    [Followup-To: news.software.readers]

    On 2022-01-15, Lewis <g.kreme@kreme.dont-email.me> wrote:
    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.

    That's a good point. While one can resize a terminal emulator window,
    one can't resize a "real" terminal, and mine has 320 columns - enough to
    make long lines impossible to read on a large monitor without danger of whiplash injuries!

    So I now agree that an option to set wrapping width would be a useful
    feature in a newsreader.

    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.

    No, but they're worth mentioning in case the nn developers are
    interested in implementing the same features.

    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?

    S-Lang scripts are an important part of the slrn experience, but the
    slrn binary is compiled from C source code. For details, see the link I provided:

    https://slrn.info/download.html


    --
    PJR :-)

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Peter J Ross@21:1/5 to Frank Slootweg on Sat Jan 15 18:58:23 2022
    XPost: alt.os.linux.slackware

    On 2022-01-15, Frank Slootweg <this@ddress.is.invalid> wrote:
    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?

    https://slrn.info/docs/slrn-manual-6.html#ss6.134

    | 6.134 wrap_method
    |
    | Type: integer
    | Default: 2
    |
    | With this variable, you can control how slrn wraps long lines. When 0,
    | it wraps at word boundries, leaving words that are longer than your line
    | width untouched. When 1, it always wraps at the right border of the
    | screen. When 2, it first tries so find a good place to wrap the line and
    | wraps at the right border only when necessary.

    (Speaking as a former maintainer and corrector of the slrn
    documentation, I wonder how I missed "boundries".)

    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.


    --
    PJR :-)

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Lewis@21:1/5 to Frank Slootweg on Sun Jan 16 01:08:20 2022
    XPost: alt.os.linux.slackware

    In message <srul7k.d68.1@ID-201911.user.individual.net> Frank Slootweg <this@ddress.is.invalid> wrote:
    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?

    There are three (as I recall) options. One looks for an 'appropriate'
    place to wrap.

    --
    I think we need to send some time apart so we know what's real and what's fox.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Michael =?ISO-8859-1?Q?B=E4uerle?=@21:1/5 to Peter J Ross on Sun Jan 16 10:12:17 2022
    Peter J Ross wrote:
    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.

    In the german hierarchy this way is common even without crosspost,
    e.g. after the topic has shifted.
    It is intended as an offer that can be accepted or rejected.

    It should be mentioned in the body in any case (because there are
    newsreaders that don't display all header fields and may execute
    Followup-To automatically).


    [Crosspost reduced, because this has nothing to do with Slackware]

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Frank Slootweg@21:1/5 to Peter J Ross on Sun Jan 16 15:33:05 2022
    XPost: alt.os.linux.slackware

    [In order not to bore/bother the Slackware audience:]
    [Followup-To: news.software.readers]

    Peter J Ross <pjr@example.invalid> wrote:
    On 2022-01-15, Frank Slootweg <this@ddress.is.invalid> wrote:

    [Thanks for the info.]

    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.

    Yes, I'll have to check the tin CHANGES file(s), but because my
    version is *very* old (from 2003), that's quite a lot of work (probably
    not if tin consistently uses the term 'pager').

    I was hoping that Urs would trigger on the use of the word 'tin' in my posting, as he often does. But if not, I'll have to get off my lazy
    butt.

    (My excuses for my old version: Don't fix what ain't broken and - more importantly - I run tin under Cygwin on (MS) Windows and updating
    Cygwin's tin or/and Cygwin itself is hard for me. I just don't quite
    'get' how to update only what needs the be updated and leave the rest untouched, That's not Cygwin's fault, just mine. (Yes, I made notes on
    how I did it the last time, but it's still hard.))

    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.

    Thanks. Yes, still mostly well, knock on wood. Good to see you too!
    Your familiar intials popping up in the last few days. :-)

    And indeed over 15 years. My 'posted' file gives a (June 5) 2005 date,
    but that file starts 'only' in (May) 2004. My earlier posting history is probably only on some DDS tape somewhere! :-) I think we go back, much
    longer than that.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From bje@ripco.com@21:1/5 to Frank Slootweg on Sun Jan 16 16:27:16 2022
    XPost: alt.os.linux.slackware

    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.

    -bruce
    bje@ripco.com

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Rich@21:1/5 to bje@ripco.com on Sun Jan 16 16:39:04 2022
    XPost: alt.os.linux.slackware

    In alt.os.linux.slackware bje@ripco.com wrote:
    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.

    That looks like joe (Joe's Own Editor). If yes, then in the "editor invocation" setting, add "-wordwrap". You can also add "-rmargin 72"
    to get a right margin of 72 characters when invoking from your news
    reader.

    In my tin here, it is line item 106 in the "menu of options" (M [upper
    case M]), and the full entry looks like this:

    106 Invocation of your editor : %E -wordwrap -rmargin 72 +%N %F

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Frank Slootweg@21:1/5 to bje@ripco.com on Sun Jan 16 18:31:31 2022
    XPost: alt.os.linux.slackware

    bje@ripco.com wrote:
    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?

    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.

    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.

    As Rich mentions, those are probably the settings of your editor, i.e.
    indeed composing an article, not reading articles.

    FYI, for composing/editing, I use the vim editor and vim can also do word-wrapping.

    But as said, my question is about (word) wrapping while reading
    (mostly other people's) articles.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Adam H. Kerman@21:1/5 to Michael Baeuerle on Sun Jan 16 20:21:30 2022
    Michael Baeuerle <michael.baeuerle@gmx.net> wrote:

    [Crosspost reduced, because this has nothing to do with Slackware]

    Thank you!

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From bje@ripco.com@21:1/5 to Frank Slootweg on Mon Jan 17 12:35:42 2022
    XPost: alt.os.linux.slackware

    In news.software.readers Frank Slootweg <this@ddress.is.invalid> wrote:

    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.


    Yeah, sorry about that, I was wrong all the way around.

    It's been so long since I compiled it, I forgot the editor tin used was called from environmental variables.

    As they say "Never mind".

    -bruce
    bje@ripco.com

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)