Hi maurice...


This is the split that had a clear 2GB limit:

K:\YT>split --version
split (GNU textutils) 2.0
Written by Torbjorn Granlund and Richard M. Stallman.

Copyright (C) 1999 Free Software Foundation, Inc.
This is free software; see the source for copying conditions. There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.

--
/|ug
https://t.me/aabolins

--- Want fido for iOS/MacOS/Android/Win/Linux? https://shrtco.de/tpJ9yV
* Origin: Fido by Telegram BBS from Stas Mishchenkov (2:460/256)

Hej Aug!

This is the split that had a clear 2GB limit:

K:\YT>split --version
split (GNU textutils) 2.0

I haven't seen the textutils version in AGES now. It has been part of coreutils for at least a decade, probably more.

<Esc>:read !split --version
split (GNU coreutils) 9.5
Copyright (C) 2024 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <https://gnu.org/licenses/gpl.html>. This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.

Written by Torbjörn Granlund and Richard M. Stallman.

Het leven is goed,
Maurice

o- o- o- o- -o o- -o o- -o o- -o -o o- o- -o o- /) /) /) /) (\ /) (\ /) (\ /) (\ (\ /) /) (\ /) ^^ ^^ ^^ ^^ ^^ ^^ ^^ ^^ ^^ ^^ ^^ ^^ ^^ ^^ ^^ ^^ ... Lieve zestien pinguïns van de Apocalyps.
--- GNU bash, version 5.2.32(1)-release (x86_64-pc-linux-gnu)
* Origin: Little Mikey's EuroPoint @ (2:280/464.113)

Hello Maurice!

K:\YT>split --version
split (GNU textutils) 2.0

I haven't seen the textutils version in AGES now. It has been part of coreutils for at least a decade, probably more.

<Esc>:read !split --version
split (GNU coreutils) 9.5
Copyright (C) 2024 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later

split started to be a requirement when I needed a command-line
way to break up a 7GB media .iso file suitable to transport on
a usb drive from my windows-based machines.

Would be nice to use a more uptodate split.exe for windows, but
split.exe 2.0 was workable when I learned (by trial and error)
what the limit was.

Meanwhile, I am very happy to see that Busybox split has no
noticeable limit for the -b parameter.

That, and the ability to do piping like:

tar | gpg | split


..luv it!



--
../|ug

--- OpenXP 5.0.58
* Origin: (2:221/1.58)

Hej August!

split started to be a requirement when I needed a command-line
way to break up a 7GB media .iso file suitable to transport on
a usb drive from my windows-based machines.

Ah! That would explain the need, although these days it is becoming hard to find usb drives less than 8G.

Would be nice to use a more uptodate split.exe for windows

The latest I could find was part of a coreutils 5.0 collection which puts it around 2003 as far as the gnu release of that version. textutils-2.0 ws released in late 1999. That is roughly +24 years ago.

Meanwhile, I am very happy to see that Busybox split has no
noticeable limit for the -b parameter.

I would definetly go with the busybox version as that is vastly more up to date.

That, and the ability to do piping like:

For sure. I use pipes all the time.

Het leven is goed,
Maurice

-o o- -o o- o- -o o- o- o- -o o- -o -o o- -o o-
(\ /) (\ /) /) (\ /) /) /) (\ /) (\ (\ /) (\ /)
^^ ^^ ^^ ^^ ^^ ^^ ^^ ^^ ^^ ^^ ^^ ^^ ^^ ^^ ^^ ^^ ... Lieve zestien pinguïns van de Apocalyps.
--- GNU bash, version 5.2.32(1)-release (x86_64-pc-linux-gnu)
* Origin: Little Mikey's EuroPoint @ (2:280/464.113)

On 16 Sep. 2024 02:43, you wrote to August:

split started to be a requirement when I needed a command-line
way to break up a 7GB media .iso file suitable to transport on
a usb drive from my windows-based machines.

Ah! That would explain the need, although these days it is becoming hard to find usb drives less than 8G.

The problem was that my usb drives needed to be FAT formated. My media player (which is about 10 yrs old now) only supports usb drives that are FAT formatted.


--- AfterShock/Android 1.7.5
* Origin: Mobile Pixel 3aXL (2:221/1.59)

Hej August!

The problem was that my usb drives needed to be FAT formated. My
media player (which is about 10 yrs old now) only supports usb
drives that are FAT formatted.

I've run across this issue many, many times. It makes me happy that I never bought one of those when they were all the rage. These days I am more likely to run into people having issues with playing mpegs and the such that are incompatible with Apple media software. I have yet to run across one of them that has issues with FAT formatted usb disks.

The more I run across these types of issues, the more I pat myself on the back with sticking with Linux all this time. I seriously doubt I could just pick it up nowadays as it took me decades to reach where I am now. Learning all this now would be impossible for me.

I can appreciate your want for a suitable split. The busybox one looks to be the winner in your situation although a properly modern gnu one would have been the best of all, were it a reality.

<Esc>:read !file /usr/bin/split
/usr/bin/split: ELF 64-bit LSB pie executable, x86-64, version 1 (SYSV), dynamically linked, interpreter /lib64/ld-linux-x86-64.so.2, for GNU/Linux 4.19.0, stripped

Gotta love it. :-)

Het leven is goed,
Maurice

-o -o -o o- o- -o o- -o o- -o -o o- o- -o -o o-
(\ (\ (\ /) /) (\ /) (\ /) (\ (\ /) /) (\ (\ /)
^^ ^^ ^^ ^^ ^^ ^^ ^^ ^^ ^^ ^^ ^^ ^^ ^^ ^^ ^^ ^^ ... Lieve zestien pinguïns van de Apocalyps.
--- GNU bash, version 5.2.32(1)-release (x86_64-pc-linux-gnu)
* Origin: Little Mikey's EuroPoint @ (2:280/464.113)

Hello Maurice,
On Tue, 17 Sep 2024 07:39:59 +0000, you wrote:

... Lieve zestien pingu∩ns van de Apocalyps.

Just a little test, no need to throw stuff at me. :)
Regards,
Nick
... Take my advice, I don't use it anyway.
--- SBBSecho 3.21-Linux
* Origin: _thePharcyde telnet://bbs.pharcyde.org (Wisconsin) (1:154/700)

Hello Maurice,
On Tue, 17 Sep 2024 07:39:59 +0000, you wrote:

... Lieve zestien pinguïns van de Apocalyps.

And another, just for fun.
Regards,
Nick
... Take my advice, I don't use it anyway.
--- SBBSecho 3.21-Linux
* Origin: _thePharcyde telnet://bbs.pharcyde.org (Wisconsin) (1:154/700)

Hej Nicholas!

Just a little test, no need to throw stuff at me. :)

<Esc>:read !trans -b -no-ansi -t dutch "You're no fun anymore."
Je bent niet meer leuk.

Het leven is goed,
Maurice

-o -o -o o- o- o- o- o- o- o- o- -o o- o- o- -o
(\ (\ (\ /) /) /) /) /) /) /) /) (\ /) /) /) (\
^^ ^^ ^^ ^^ ^^ ^^ ^^ ^^ ^^ ^^ ^^ ^^ ^^ ^^ ^^ ^^ ... Lieve zestien pinguïns van de Apocalyps.
--- GNU bash, version 5.2.37(1)-release (x86_64-pc-linux-gnu)
* Origin: Little Mikey's EuroPoint @ (2:280/464.113)

Hello Maurice,
On Wed, 13 Nov 2024 17:36:51 +0000, you wrote:

Just a little test, no need to throw stuff at me. :)

<Esc>:read !trans -b -no-ansi -t dutch "You're no fun anymore."
Je bent niet meer leuk.

I'm trying to get this program not to scrunch the empty lines out of my replies. :/

... Lieve zestien pinguïns van de Apocalyps.

And to make sure that UTF-8 is still working as expected. :)
Regards,
Nick
... Take my advice, I don't use it anyway.
--- SBBSecho 3.21-Linux
* Origin: _thePharcyde telnet://bbs.pharcyde.org (Wisconsin) (1:154/700)

Hello Maurice,

On Wed, 13 Nov 2024 17:36:51 +0000, you wrote:

<Esc>:read !trans -b -no-ansi -t dutch "You're no fun anymore."
Je bent niet meer leuk.

Looks great when I'm writing it, then it changes after I hit send. Maybe this time, it'll work.

... Lieve zestien pinguïns van de Apocalyps.

In between quoted text seems to work fine, so here's an attempt to add a blank space on each empty line.. which shouldn't be necessary!

Regards,
Nick

... Take my advice, I don't use it anyway.
--- SBBSecho 3.21-Linux
* Origin: _thePharcyde telnet://bbs.pharcyde.org (Wisconsin) (1:154/700)

Hey Nicholas!

I'm trying to get this program not to scrunch the empty lines out
of my replies. :/

I just checked your raw pkt and everything looks as it should, including blank lines. Some older versions of synchro were putting '\n' characters instead of '\r' characters which is a no-no according to ftn standards for the msg_body().

... Lieve zestien pinguïns van de Apocalyps.

And to make sure that UTF-8 is still working as expected. :)

The first one was bonky but as you can see above it is all fine now.

Life is good,
Maurice

o- o- -o o-
/) /) (\ /)
^^ ^^ ^^ ^^
... Druncen beorg þe ond dollic word.
Guard against drunkenness and foolish words.
--- GNU bash, version 5.2.32(1)-release (x86_64-pc-linux-gnu)
* Origin: Little Mikey's Brain - Ladysmith BC, Canada (1:153/7001)

Hello Maurice,
On Wed, 13 Nov 2024 18:14:44 +0000, you wrote:

I just checked your raw pkt and everything looks as it should, including blank lines. Some older versions of synchro were putting '\n' characters instead of '\r' characters which is a no-no according to ftn standards for the msg_body().

Except for the missing blank lines that I should have had in the message. The Synchronet thing you mention was quite some time ago. In this example, I'm trying out a newsreader on Synchronet's NNTP server.

... Lieve zestien pinguïns van de Apocalyps.

And to make sure that UTF-8 is still working as expected. :)

The first one was bonky but as you can see above it is all fine now.

For the record/example, the two lines you just quoted here should have had a blank line between them. The testing continues, I suppose.
Regards,
Nick
... Take my advice, I don't use it anyway.
--- SBBSecho 3.21-Linux
* Origin: _thePharcyde telnet://bbs.pharcyde.org (Wisconsin) (1:154/700)

Hello Maurice,

On Wed, 13 Nov 2024 18:14:44 +0000, you wrote ..

I just checked your raw pkt and everything looks as it should, including blank lines. Some older versions of synchro were putting '\n' characters instead of '\r' characters which is a no-no according to ftn standards for the msg_body().

It's not that I'm replying to this again, I'm just using it for formatting and placement.

The first one was bonky but as you can see above it is all fine now.

The first one, I didn't forcefully set UTF-8 to outgoing messages. I was hoping that the program set to "Auto" would pick up on your UTF-8 character that I quoted and automagically detect what to write back with. Needless to say, that failed miserably. Sometimes you just can't win.

Regards,
Nick

... Take my advice, I don't use it anyway.
--- SBBSecho 3.21-Linux
* Origin: _thePharcyde telnet://bbs.pharcyde.org (Wisconsin) (1:154/700)

Hello Maurice,

On Wed, Nov 13 2024 12:14:44 -0600, you wrote:

The first one was bonky but as you can see above it is all fine now.

Luckily, the last one I sent out worked as expected. For some reason, setting the "Template" globally worked much better than trying to set it on a per account basis.

Now with all that said and done, FYI I'm posting this one with vim. Recently, I figured I'd give it a go since it has a few formatting features I was interested in, mainly 'gq' to wrap long lines which also preserves the quote character and adds it to the rest of the newly wrapped paragraph.

However, I don't care for 'Xdd' nearly as much as CTRL-K and CTRL-U from nano (cut and paste, basically). Unless there's another way to do it that I haven't found yet.

With this one, I got to sneak another test in there to make sure slrn isn't sending this message to 'All', after manually setting the X-Comment-To header. :)

Regards,
Nick

... He who laughs last, thinks slowest.
--- SBBSecho 3.21-Linux
* Origin: _thePharcyde telnet://bbs.pharcyde.org (Wisconsin) (1:154/700)

Hey Nicholas!

I'm just using it for formatting and placement.

Best of them thus far, not counting the vim one which allows the end user to decide what is 'proper' word wrapping. It seems to me that you had nano doing this as well and to be honest I think that would be most suitable to the DOS-think types. I need to have another looksee of the latest nano.

Sometimes you just can't win.

At my age I'd be more than happy if I break out even. :-/

Life is good,
Maurice

o- -o o- o- -o o- o- -o -o o- o- o- o- o- o- o- /) (\ /) /) (\ /) /) (\ (\ /) /) /) /) /) /) /) ^^ ^^ ^^ ^^ ^^ ^^ ^^ ^^ ^^ ^^ ^^ ^^ ^^ ^^ ^^ ^^ ... Fidonet 4K - You load sixteen penguins and what do you get?
--- GNU bash, version 5.2.37(1)-release (x86_64-pc-linux-gnu)
* Origin: One of us @ (1:153/7001.2989)

Hello Maurice,

On Wed, Nov 13 2024 16:26:25 -0600, you wrote:

Best of them thus far, not counting the vim one which allows the end user to decide what is 'proper' word wrapping. It seems to me that you had nano doing this as well and to be honest I think that would be most suitable to the DOS-think types. I need to have another looksee of the latest nano.

I don't believe nano can word wrap on the fly with any kind of key combination (as compared to 'gq' in vim). It's more of a configuration setting that does it when you envoke the editor.

However, with long, unwrapped lines.. even if you softwrap with nano, it's still a long line. So if you quote that line, it it will only place one quote character at the beginning of the paragraph (since it's still one line).

Vim will wrap where you want it to, as well as include the quote character at the beginning of each wrapped line. Pretty impressive, I might say!

At my age I'd be more than happy if I break out even. :-/

Hopefully there's plenty of good years left to keep those numbers up. :)

Regards,
Nick

... He who laughs last, thinks slowest.
--- SBBSecho 3.22-Linux
* Origin: _thePharcyde telnet://bbs.pharcyde.org (Wisconsin) (1:154/700)

Hey Nicholas!

Vim will wrap where you want it to, as well as include the quote
character at the beginning of each wrapped line.

'fold -s -w 67' will wrap with the space at the end of the line, except the last line as shown above. I tacked in the qoute prefix at the start of the lines using sed. I've been doing it the way since forever and old habits die hard. The only issue I had was when I first started using utf-8 characters but that was resolved long before utf-8 became the default for me and mine.

Hopefully there's plenty of good years left to keep those numbers up.

Agreed. As long as I can still care for myself I have no plans to give up the good fight.

For the record;

<Esc>:read !vim --version
VIM - Vi IMproved 9.1 (2024 Jan 02, compiled Nov 11 2024 06:21:11)
Included patches: 1-813
Compiled by root@bitskii
Huge version without GUI. Features included (+) or not (-):
+acl +file_in_path +mouse_urxvt -tag_any_white
+arabic +find_in_path +mouse_xterm -tcl
+autocmd +float +multi_byte +termguicolors +autochdir +folding +multi_lang +terminal -autoservername -footer -mzscheme +terminfo -balloon_eval +fork() +netbeans_intg +termresponse +balloon_eval_term -gettext +num64 +textobjects
-browse -hangul_input +packages +textprop ++builtin_terms +iconv +path_extra +timers
+byte_offset +insert_expand -perl +title
+channel +ipv6 +persistent_undo -toolbar
+cindent +job +popupwin +user_commands -clientserver +jumplist +postscript +vartabs
-clipboard +keymap +printer +vertsplit +cmdline_compl +lambda +profile +vim9script +cmdline_hist +langmap -python +viminfo
+cmdline_info +libcall -python3 +virtualedit
+comments +linebreak +quickfix +visual
+conceal +lispindent +reltime +visualextra
+cryptv +listcmds +rightleft +vreplace
+cscope +localmap -ruby +wildignore +cursorbind -lua +scrollbind +wildmenu
+cursorshape +menu +signs +windows
+dialog_con +mksession +smartindent +writebackup
+diff +modify_fname -sodium -X11
+digraphs +mouse -sound +xattr
-dnd -mouseshape +spell -xfontset
-ebcdic +mouse_dec +startuptime -xim
+emacs_tags -mouse_gpm +statusline -xpm
+eval -mouse_jsbterm -sun_workshop -xsmp
+ex_extra +mouse_netterm +syntax -xterm_clipboard +extra_search +mouse_sgr +tag_binary -xterm_save
-farsi -mouse_sysmouse -tag_old_static
system vimrc file: "/etc/vimrc"
user vimrc file: "$HOME/.vimrc"
2nd user vimrc file: "~/.vim/vimrc"
3rd user vimrc file: "~/.config/vim/vimrc"
user exrc file: "$HOME/.exrc"
defaults file: "$VIMRUNTIME/defaults.vim"
fall-back for $VIM: "/usr/share/vim"
Compilation: gcc -c -I. -Iproto -DHAVE_CONFIG_H -g -O2 -D_REENTRANT -U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=1
Linking:
gcc -L/usr/local/lib -Wl,--as-needed -o vim -lm -lncurses -lacl -lattr

Life is good,
Maurice

-o o- -o o- -o o- o- o- o- o- -o o- o- o- o- -o
(\ /) (\ /) (\ /) /) /) /) /) (\ /) /) /) /) (\
^^ ^^ ^^ ^^ ^^ ^^ ^^ ^^ ^^ ^^ ^^ ^^ ^^ ^^ ^^ ^^ ... Fidonet 4K - You load sixteen penguins and what do you get?
--- GNU bash, version 5.2.37(1)-release (x86_64-pc-linux-gnu)
* Origin: One of us @ (1:153/7001.2989)

Hello Maurice,

On Fri, Nov 15 2024 10:32:37 -0600, you wrote:

Vim will wrap where you want it to, as well as include the quote character at the beginning of each wrapped line.

'fold -s -w 67' will wrap with the space at the end of the line, except the last line as shown above. I tacked in the qoute prefix at the start of the lines using sed. I've been doing it the way since forever and old habits die hard. The only issue I had was when I first started using utf-8 characters but that was resolved long before utf-8 became the default for me and mine.

Yes, I know about fold and sed. I started messing with both of those while still using nano, but after the second quote level I'd had enough. I don't know sed well enough to be able to figure it out easily. One command took me hours to figure out and get to work right.

At that point, in desparation, I tried out vim. Once I noticed that 'gq' will not only wrap a long line, but will also automatically insert the quote character at the beginning of every line that was wrapped, I figured this may be an easier approach for me. :)

For the record;

<Esc>:read !vim --version
VIM - Vi IMproved 9.1 (2024 Jan 02, compiled Nov 11 2024 06:21:11)
Included patches: 1-813

Now you have me wondering what that command does!

<Esc>:read !vim --version
VIM - Vi IMproved 9.1 (2024 Jan 02, compiled Oct 15 2024 14:18:26)
Included patches: 1-785
Compiled by Arch Linux
Huge version without GUI. Features included (+) or not (-):
+acl +file_in_path +mouse_urxvt -tag_any_white
+arabic +find_in_path +mouse_xterm +tcl/dyn
+autocmd +float +multi_byte +termguicolors +autochdir +folding +multi_lang +terminal -autoservername -footer -mzscheme +terminfo -balloon_eval +fork() +netbeans_intg +termresponse +balloon_eval_term +gettext +num64 +textobjects
-browse -hangul_input +packages +textprop ++builtin_terms +iconv +path_extra +timers
+byte_offset +insert_expand +perl/dyn +title
+channel +ipv6 +persistent_undo -toolbar
+cindent +job +popupwin +user_commands -clientserver +jumplist +postscript +vartabs
-clipboard +keymap +printer +vertsplit +cmdline_compl +lambda +profile +vim9script +cmdline_hist +langmap -python +viminfo
+cmdline_info +libcall +python3/dyn +virtualedit
+comments +linebreak +quickfix +visual
+conceal +lispindent +reltime +visualextra
+cryptv +listcmds +rightleft +vreplace
+cscope +localmap +ruby/dyn +wildignore +cursorbind +lua/dyn +scrollbind +wildmenu
+cursorshape +menu +signs +windows
+dialog_con +mksession +smartindent +writebackup
+diff +modify_fname -sodium -X11
+digraphs +mouse -sound +xattr
-dnd -mouseshape +spell -xfontset
-ebcdic +mouse_dec +startuptime -xim
+emacs_tags +mouse_gpm +statusline -xpm
+eval -mouse_jsbterm -sun_workshop -xsmp
+ex_extra +mouse_netterm +syntax -xterm_clipboard +extra_search +mouse_sgr +tag_binary -xterm_save
-farsi -mouse_sysmouse -tag_old_static
system vimrc file: "/etc/vimrc"
user vimrc file: "$HOME/.vimrc"
2nd user vimrc file: "~/.vim/vimrc"
3rd user vimrc file: "~/.config/vim/vimrc"
user exrc file: "$HOME/.exrc"
defaults file: "$VIMRUNTIME/defaults.vim"
fall-back for $VIM: "/usr/share/vim"
Compilation: gcc -c -I. -Iproto -DHAVE_CONFIG_H -march=x86-64 -mtune=generic -O2 -pipe -fno-plt -fexceptions -Wformat -Werror=format-security -fstack-clash-protection -fcf-protection -fno-omit-frame-pointer -mno-omit-leaf-frame-pointer -g -ffile-prefix-map=/build/vim/src=/usr/src/debug/vim -flto=auto -D_REENTRANT -U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=1
Linking: gcc -Wl,-E -Wl,-rpath,/usr/lib/perl5/5.40/core_perl/CORE -Wl,-O1 -Wl,--sort-common -Wl,--as-needed -Wl,-z,relro -Wl,-z,now -Wl,-z,pack-relative-relocs -flto=auto -L/usr/local/lib -o vim -lm -ltinfo -lacl -lattr -lgpm -L/usr/lib -ltclstub8.6 -ldl -lz -lpthread -lm

Ooh, neat-o!

Regards,
Nick

... He who laughs last, thinks slowest.
--- SBBSecho 3.22-Linux
* Origin: _thePharcyde telnet://bbs.pharcyde.org (Wisconsin) (1:154/700)

Hey Nicholas!

Once I noticed that 'gq' will not only wrap a long line, but will
also automatically insert the quote character at the beginning of
every line that was wrapped

I am sure that is what mutt does which is what I use for email. I used to use pine back in the Triassic, whose default editor was pico, which is the grandfather to nano. I believe it used the same strategy for quoting as vim. To be honest I prefer the fold/sed quoting seen above which it far more fido-ish as well as bashist as any old hack in-the-know will verify I am sure.

+mouse_gpm

I would (and do) turn that off using the --disable-gpm to vim's configure. Same with in mc (mcedit). That way cutting and pasting from other consoles is vastly more usable. vim doesn't need no stinkin' mouse.

Ooh, neat-o!

For sure. For creating manpages or info files it is a godsend. As a bonus it works great for dumping information straight into a msg like thus;

<Esc>:read !trans -b -no-ansi -t ukrainian "Strong like bull, smart like tractor."
Сильний, як бик, розумний, як трактор.

Gotta love it.

Life is good,
Maurice

o- -o o- o- o- o- o- o- o- -o o- -o o- o- o- -o /) (\ /) /) /) /) /) /) /) (\ /) (\ /) /) /) (\ ^^ ^^ ^^ ^^ ^^ ^^ ^^ ^^ ^^ ^^ ^^ ^^ ^^ ^^ ^^ ^^ ... Fidonet 4K - You load sixteen penguins and what do you get?
--- GNU bash, version 5.2.37(1)-release (x86_64-pc-linux-gnu)
* Origin: One of us @ (1:153/7001.2989)

Hello Maurice,

On Sat, Nov 16 2024 19:34:35 -0600, you wrote:

I am sure that is what mutt does which is what I use for email. I used to use pine back in the Triassic, whose default editor was pico, which is the grandfather to nano. I believe it used the same strategy for quoting as vim. To be honest I prefer the fold/sed quoting seen above which it far more fido-ish as well as bashist as any old hack in-the-know will verify I am sure.

If nano still has something like that, I would love to know about it. But with all that said, if you care to share your fold/sed quoting mastery, I would love to take a look at it and possibly try to implement it here!

+mouse_gpm

I would (and do) turn that off using the --disable-gpm to vim's configure. Same with in mc (mcedit). That way cutting and pasting from other consoles is vastly more usable. vim doesn't need no stinkin' mouse.

I don't mind mouse support. Especially since I'm using putty to ssh into my Linux VMs hosted on my server machine from a Windows 11 desktop. I can copy from Windows and use right click in any of my Linux consoles, no matter what program I'm running, to paste. It works great!

<Esc>:read !trans -b -no-ansi -t ukrainian "Strong like bull, smart like tractor."
Сильний, як бик, розумний, як трактор.

Gotta love it.

I do, I do. I'll have to study up on that more when I get a chance. At the moment I don't have trans installed as I've never had to use it before. That's about to change, though. :)

Regards,
Nick

... He who laughs last, thinks slowest.
--- SBBSecho 3.22-Linux
* Origin: _thePharcyde telnet://bbs.pharcyde.org (Wisconsin) (1:154/700)

Hello Maurice,

On Sat, Nov 16 2024 19:34:35 -0600, you wrote:

<Esc>:read !trans -b -no-ansi -t ukrainian "Strong like bull, smart like tractor."
Сильний, як бик, розумний, як трактор.

<Esc>:read !trans -b -no-ansi -t japanese "Strong like bull, smart like tractor."
雄牛のように強く、トラクターのように賢い。

Possibilities are endless. :)

Regards,
Nick

... He who laughs last, thinks slowest.
--- SBBSecho 3.22-Linux
* Origin: _thePharcyde telnet://bbs.pharcyde.org (Wisconsin) (1:154/700)

Hey Nicholas!

If nano still has something like that, I would love to know about
it.

I haven't looked into it but my best guess is that it might have something to do with alpine, which is (was?) the replacement for pine. Beats me if it is still supported. University of Washington if I am not mistaken.

if you care to share your fold/sed quoting mastery

How deep do you wish me to delve into it? At the moment it is part and parcel of a bash script that does it all, reply-wise. I forget the last time I did any serious work on it and it will take me some time to isolate just the quoting aspect. It is doable though since it started out as an isolated bit of code and I might even have a backup of that initial work which if true will speed up the process.

That's about to change, though.

I noticed. What version are you deploying?

<Esc>:read !trans -no-ansi -version
Translate Shell 0.9.7.1

platform Linux
terminal type linux
bi-di emulator [N/A]
gawk (GNU Awk) 5.3.1
fribidi (GNU FriBidi) 1.0.16
audio player mpv --no-config
terminal pager less
web browser xdg-open
user locale C.utf8 (English)
host language en
source language auto
target language en
translation engine auto
proxy [NONE]
user-agent Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/104.0.0.0 Safari/537.36 Edg/104.0.1293.54
ip version [DEFAULT]
theme default
init file [NONE]

Report bugs to: https://github.com/soimort/translate-shell/issues

<Esc>:read !trans -no-ansi -list-languages-english
Afrikaans
Albanian
Amharic
Arabic
Armenian
Assamese
Aymara
Azerbaijani
Bambara
Bashkir
Basque
Belarusian
Bengali
Bhojpuri
Bosnian
Bulgarian
Cantonese
Catalan
Cebuano
Chichewa
Chinese (Literary)
Chinese (Simplified)
Chinese (Traditional)
Chuvash
Corsican
Croatian
Czech
Danish
Dari
Dhivehi
Dogri
Dutch
Eastern Mari
English
Esperanto
Estonian
Ewe
Faroese
Fijian
Filipino
Finnish
French
French (Canadian)
Frisian
Galician
Georgian
German
Greek
Guarani
Gujarati
Haitian Creole
Hausa
Hawaiian
Hebrew
Hill Mari
Hindi
Hmong
Hungarian
Icelandic
Igbo
Ilocano
Indonesian
Inuinnaqtun
Inuktitut
Inuktitut (Latin)
Irish
Italian
Japanese
Javanese
Kannada
Kazakh
Khmer
Kinyarwanda
Klingon
Konkani
Korean
Krio
Kurdish (Central)
Kurdish (Northern)
Kyrgyz
Lao
Latin
Latvian
Lingala
Lithuanian
Luganda
Luxembourgish
Macedonian
Maithili
Malagasy
Malay
Malayalam
Maltese
Maori
Marathi
Meiteilon
Mizo
Mongolian
Mongolian (Traditional)
Myanmar
Nepali
Norwegian
Odia
Oromo
Papiamento
Pashto
Persian
Polish
Portuguese (Brazilian)
Portuguese (European)
Punjabi
Quechua
Querétaro Otomi
Romanian
Russian
Samoan
Sanskrit
Scots Gaelic
Sepedi
Serbian (Cyrillic)
Serbian (Latin)
Sesotho
Shona
Sindhi
Sinhala
Slovak
Slovenian
Somali
Spanish
Sundanese
Swahili
Swedish
Tahitian
Tajik
Tamil
Tatar
Telugu
Thai
Tibetan
Tigrinya
Tongan
Tsonga
Turkish
Turkmen
Twi
Udmurt
Ukrainian
Upper Sorbian
Urdu
Uyghur
Uzbek
Vietnamese
Welsh
Xhosa
Yakut
Yiddish
Yoruba
Yucatec Maya
Zulu

Definetly overkill for so-called 'supported' fidonet languages. :-)

Life is good,
Maurice

o- -o o- o- o- o- o- -o o- o- o- -o o- o- -o -o /) (\ /) /) /) /) /) (\ /) /) /) (\ /) /) (\ (\ ^^ ^^ ^^ ^^ ^^ ^^ ^^ ^^ ^^ ^^ ^^ ^^ ^^ ^^ ^^ ^^ ... Fidonet 4K - You load sixteen penguins and what do you get?
--- GNU bash, version 5.2.37(1)-release (x86_64-pc-linux-gnu)
* Origin: One of us @ (1:153/7001.2989)

Hey Nicholas!

Possibilities are endless. :)

Not quite endless but certainly far beyond fidonet's support system ... to say the least.

It would be nice to see a Japanese reaction to your translation. What are the odds that we do?

Life is good,
Maurice

o- -o -o o- -o o- -o o- o- -o o- o- o- o- o- o- /) (\ (\ /) (\ /) (\ /) /) (\ /) /) /) /) /) /) ^^ ^^ ^^ ^^ ^^ ^^ ^^ ^^ ^^ ^^ ^^ ^^ ^^ ^^ ^^ ^^ ... Fidonet 4K - Sweet Sixteen Penguins of the Apocalypse.
--- GNU bash, version 5.2.37(1)-release (x86_64-pc-linux-gnu)
* Origin: One of us @ (1:153/7001.2989)

Hello Maurice,

On Sun, Nov 17 2024 00:38:32 -0600, you wrote:

How deep do you wish me to delve into it? At the moment it is part and parcel of a bash script that does it all, reply-wise. I forget the last time I did any serious work on it and it will take me some time to isolate just the quoting aspect. It is doable though since it started out as an isolated bit of code and I might even have a backup of that initial work which if true will speed up the process.

Probably just the quoting part. I'm currently using slrn (a console based NNTP newsreader) that handles the messages themselves. When I reply/follow-up to a message it craps the message out to a text file which I pick up in vim or nano. Obviously, standard newsreader quoting etiquette is applied with no fancy FTN stuff going on.

That's about to change, though.

I noticed. What version are you deploying?

<Esc>:read !trans -no-ansi -version
Translate Shell 0.9.7.1

<Esc>:read !trans -no-ansi -version
Translate Shell 0.9.7.1-git:faff2c9

platform Linux
terminal type xterm
bi-di emulator [N/A]
gawk (GNU Awk) 5.3.1
fribidi (GNU FriBidi) [NOT INSTALLED]
audio player mpg123
terminal pager less
web browser xdg-open
user locale en_US.UTF-8 (English)
host language en
source language auto
target language en
translation engine auto
proxy [NONE]
user-agent Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/104.0.0.0 Safari/537.36 Edg/104.0.1293.54
ip version [DEFAULT]
theme default
init file [NONE]

Report bugs to: https://github.com/soimort/translate-shell/issues

Looks promising!

Definetly overkill for so-called 'supported' fidonet languages. :-)

I'd say! This program could definitely help out the yearly UTF-8 "Merry Christmas/Happy New Year" post by possibly dang near doubling it. :)

While reading the list of languages in your post (I'll assume mine is close to the same, so refrained from posting it), I caught "Javanese" and had to look it up. Learn something new every day! :)

Regards,
Nick

... He who laughs last, thinks slowest.
--- SBBSecho 3.22-Linux
* Origin: _thePharcyde telnet://bbs.pharcyde.org (Wisconsin) (1:154/700)

Hello Maurice,

On Sun, Nov 17 2024 01:03:50 -0600, you wrote:

Not quite endless but certainly far beyond fidonet's support system ... to say the least.

Probably far beyond either of our scope, let alone just Fidonet, as well.

It would be nice to see a Japanese reaction to your translation. What are the odds that we do?

Slim to none, probably. :)

Regards,
Nick

... He who laughs last, thinks slowest.
--- SBBSecho 3.22-Linux
* Origin: _thePharcyde telnet://bbs.pharcyde.org (Wisconsin) (1:154/700)

Hey Nicholas!

Probably just the quoting part.

That is what I thought. This week is going to be bad for me as I have many medical issues to deal with but I promise I'll post something generic that could potentially work across the board with a bit of tweaking.

In the meantime I think your current strategy is sound but I'd suggest setting the line length to 72 characters so that when someone with a more limited application quotes back a quote the line will still fit into one line. I note one of August's replies to you is a tad wonky when using a 79 character line length.

Life is good,
Maurice

-o o- o- -o
(\ /) /) (\
^^ ^^ ^^ ^^
... Is nu þes middangeard mane geblonden, wanað ond weaxeð.
Now is this world blended with evils; it wanes and waxes.
--- GNU bash, version 5.2.32(1)-release (x86_64-pc-linux-gnu)
* Origin: Little Mikey's Brain - Ladysmith BC, Canada (1:153/7001)

Hello Maurice,

On Sun, Nov 17 2024 17:42:35 -0600, you wrote:

That is what I thought. This week is going to be bad for me as I have
many medical issues to deal with but I promise I'll post something
generic that could potentially work across the board with a bit of
tweaking.

No worries. Your health comes first. I've gone this far without anything like it, so I'm sure I can wait until you have the time. :)

In the meantime I think your current strategy is sound but I'd suggest setting the line length to 72 characters so that when someone with a
more limited application quotes back a quote the line will still fit
into one line. I note one of August's replies to you is a tad wonky
when using a 79 character line length.

Bah! "Limited applications.."

set fo-=t
set textwidth=72

.. in .vimrc seems to do the trick.

Regards,
Nick

... He who laughs last, thinks slowest.
--- SBBSecho 3.22-Linux
* Origin: _thePharcyde telnet://bbs.pharcyde.org (Wisconsin) (1:154/700)