This is the split that had a clear 2GB limit:
K:\YT>split --version
split (GNU textutils) 2.0
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
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:
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.
... Lieve zestien pingu∩ns van de Apocalyps.Just a little test, no need to throw stuff at me. :)
... Lieve zestien pinguïns van de Apocalyps.And another, just for fun.
Just a little test, no need to throw stuff at me. :)
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.
... Lieve zestien pinguïns van de Apocalyps.And to make sure that UTF-8 is still working as expected. :)
<Esc>:read !trans -b -no-ansi -t dutch "You're no fun anymore."Looks great when I'm writing it, then it changes after I hit send. Maybe this time, it'll work.
Je bent niet meer leuk.
... Lieve zestien pinguïns van de Apocalyps.
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. :)
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.
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().
The first one was bonky but as you can see above it is all fine now.
The first one was bonky but as you can see above it is all fine now.
I'm just using it for formatting and placement.
Sometimes you just can't win.
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.
At my age I'd be more than happy if I break out even. :-/
Vim will wrap where you want it to, as well as include the quote
character at the beginning of each wrapped line.
Hopefully there's plenty of good years left to keep those numbers up.
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.
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
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
+mouse_gpm
Ooh, neat-o!
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.
<Esc>:read !trans -b -no-ansi -t ukrainian "Strong like bull, smart like tractor."
Сильний, як бик, розумний, як трактор.
Gotta love it.
<Esc>:read !trans -b -no-ansi -t ukrainian "Strong like bull, smart like tractor."
Сильний, як бик, розумний, як трактор.
If nano still has something like that, I would love to know about
it.
if you care to share your fold/sed quoting mastery
That's about to change, though.
Possibilities are endless. :)
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
Definetly overkill for so-called 'supported' fidonet languages. :-)
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?
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.
No worries. Your health comes first.
Still require more testing. So far they haven't figured it out. On
the plus side, I am still not dead, although mother nature is
throwing some very nasty weather in this direction.
... Lieve zestien pinguïns van de Apocalyps.Regards,
What exactly are they trying to figure out?
We just got our first light blizzard on Thursday.
I am not sure ... near as I can tell cancer which so far isn't
showing up in any of the tests/probing thus far. What I know for
sure is that my hemoglobin levels have been dangerously low which
all the specialists claim is due to internal bleeding which so far
they cannot find. I have one more probing of my small intestine to
go through in a couple of weeks that might tell the tale. In the
meantime I have to go to the hospital every few weeks or so to
recieve blood tranfusions.
We just got our first light blizzard on Thursday.
Tis the season. I grew up on the prairies (Saskatchewan) so I know
how bad they can get. If I recall correctly, January blizzards were
the worst. It makes me shiver just thinking about it. On the plus
side I still have all my body parts. I've met many who weren't so
lucky and lost fingers and/or toes or worse after being caught in a
blizzard.
Here's hoping you finish off strong and come out with a clean
bill of health.
In the trades you spend a lot of money on clothing this time of
year so that you keep all of your body parts.
Like the saying goes, strong like bull, smart like tractor. :-)
In the trades you spend a lot of money on clothing this time of
year so that you keep all of your body parts.
Here on the west coast, keeping dry is three quarters of the battle. Half-decent clothing that keeps you dry and warm doesn't come cheap,
to say the least.
With the crazy rush on AI, "tractor" above may indeed become
"human" very soon!
With the crazy rush on AI, "tractor" above may indeed become
"human" very soon!
Unless tractors go extinct, I seriously doubt humans will ever
replace them ... AI or not.
I meant the words in the sentence would change
AI, which will soon be controlling said tractor
I meant the words in the sentence would change
I understood without further explanation but thought it would be
more fun if perhaps responding like an AI robot might.
AI, which will soon be controlling said tractor
It's been done. Same with other machinery including cars. Without
human oversight and intervention when needed, I doubt it would last
long. I also doubt that AI really cares one way or another.
Haven't you ever seen the "Terminator" series of movies?
When the machines take over, we're all screwed. :)
| Sysop: | Nitro |
|---|---|
| Location: | Portland, OR |
| Users: | 4 |
| Nodes: | 10 (0 / 10) |
| Uptime: | 218:16:23 |
| Calls: | 139 |
| Files: | 752 |
| Messages: | 87,387 |