<jack-sparrow>
but what is the operation level of sound ?
<jack-sparrow>
i would try to do an icecast server, may be on haiki-os
<jack-sparrow>
haiku-os
<jack-sparrow>
you do a beautifull work
<jack-sparrow>
if can i have the sound may be i stay on haiku-os
OscarL has joined #haiku
<jack-sparrow>
i have an audiobox usb card
<scanty>
oh hi OscarL
* OscarL
politely points out the OS name is just Haiku
<OscarL>
Hello there scanty :-)
<scanty>
how are you feeling today?
<OscarL>
jack-sparrow: regarding icecast... if I'm not mistaken, phschafft knows a thing or two about that.
<jack-sparrow>
with two input in jack 6.35/XLR an mixer between input output and headphone outuput en monitor hi-fi output too
<jack-sparrow>
ardour work on haiku ?
<OscarL>
scanty: "normal", which is good :-). Have been doing some clean up around the house, planting a couple of trees, can't complain much... except for international news... I should take a vacation from those :-/.
<jack-sparrow>
no ardour
<scanty>
normal is good :-) i had to do a blood test today... other than that nothing going on here.
<jack-sparrow>
no idjc
<OscarL>
scanty: how about you, pal?
<scanty>
except this weird tile drawing bug.
<jack-sparrow>
i desapare, haiku-os not ready to MAO
<scanty>
OscarL: i'm doing quite well, thanks.
<scanty>
"normal" :-)
<OscarL>
heh, darn little bugs are persistent (both in software and in brain, at least here :-P)
<scanty>
i know what the problem is, i'm just not certain how to fix it.
<scanty>
it *could* be a haiku issue, which is why i have someone use the same code in Qt, and see if it works as is.
<OscarL>
wish I could do more than provide moral support.
<scanty>
yeah.
<OscarL>
let's hope that with a bit more time into it... you'll find either a proper solution, or at least a decent workaround :-)
<OscarL>
mmm, our icecast is 3.5+ years old... guess we don't have many people using it.
<scanty>
yeah, i have been working on this for too long, and i have other things i want to work on, but i need to finish this first.
vdamewood has quit [Quit: My Mac has gone to sleep. ZZZzzz…]
<OscarL>
("Icecast Current Release (2.4.4)" seems we're still good there anyway, LOL)
<OscarL>
sometimes is good to take a step back, or focus on something else (specially something where you can make progress).
<phschafft>
OscarL: psssst! ;)
<OscarL>
(on the other hand... there's the risk of having to many started projects and not completing any :-D)
<phschafft>
OscarL: 2.5 rc1 is currently on it's way out.
<phschafft>
and whoever is the downstream maintainer should have a look at 2.5.x, as 2.4.x will soon have some end of life notice one way or another.
<OscarL>
good to know! depedencies list is not too bad, so I may update the recipe unless I forget about it :-D
<phschafft>
also note that 2.5.x can read 2.4.x config files with no problems.
<phschafft>
but web/ and admin/ needs to be up-to-date.
<phschafft>
which should be no problem unless someone manually changed their copies.
<phschafft>
I think on the dependency list libigloo and librhash is new.
<OscarL>
"rhash_devel 1.4.4-3" on repos...
<OscarL>
seems we don't have a recipe for igloo.
<phschafft>
rhash is tested at least down to v1.3.3.
<OscarL>
well... let's see how long it takes me to package libigloo.
<OscarL>
brb, need to restart the phone,
OscarL has quit []
mmu_man has quit [Ping timeout: 480 seconds]
OrangeBomb has quit [Read error: Connection reset by peer]
OscarL has joined #haiku
OrangeBomb has joined #haiku
mmu_man has joined #haiku
<OscarL>
had to chase the git repo from Ubuntu's libigloo page :-/
<scanty>
damn, out of everything good to drink. it's nice out but i don't feel like going to the store.
<scanty>
sorry thinking out loud.
<OscarL>
don't worry :-). Similar thinking here scanty :-D
<scanty>
:-)
<OscarL>
gitlab UI is not good. turns out you need to hit ENTER *twice* for the search to find repos. sigh.
<scanty>
lols
<OscarL>
no wonder I couldn't find libigloo :-D
<scanty>
who knew an extra keystroke would be a dealbreaker
<OscarL>
I mean... I already dislike gitlab's UI in general, this just adds insult to injury.
<scanty>
i haven't heard of gitlab until just now.
<scanty>
OscarL: BTW, getting used to pianobar -- thinking about a proper Haiku port if i have the motivation and time.
<phschafft>
considering the structure of the foundation I'm very happy to have at least gitlab. ;)
<phschafft>
it's by far not a perfect tool. but it can do what the foundation needs. plus it's self hosted.
<OscarL>
considering what they work on... one would expect Xiph the to be a strong and sound foundation.
<OscarL>
:-P
<scanty>
OscarL: i was ready to test your peek/poke driver, but i can't find a parallel port cable yet.
<scanty>
i haven't looked everywhere.
<OscarL>
I have about 30 m of the stuff... too bad shipping would be killer :-D
<scanty>
wow.
<scanty>
i just need like 1.5m
<phschafft>
OscarL: ;)
<phschafft>
I'm not sure when I last used a parallel port. likely the 90s?
<phschafft>
but hey, the machine I write from right now has one!
<OscarL>
I was using it for direct cable connection in 2002, that's why I have one of about 15m :-D (we were too poor for a proper LAN, and got the cable for free, so...)
<scanty>
wow
<phschafft>
I was on SCSI and then 10BaseT, 100BaseT, and now 1000BaseT
<phschafft>
so now my network is back at the same speed as it was initially ;)
<OscarL>
(cable was from telephone lines from a building undergoing renovations, just needed to do some soldering... free network! :-D)
<phschafft>
haha.
<OscarL>
I remember reading about SCSI a lot back in the day... but never actually saw any hardware using it :-(
<phschafft>
hm.
<phschafft>
it was fun. just that people seem to remember it only for attaching disks. but it was more like USB in what it could do.
<phschafft>
e.g. also very common were SCSI scanners.
<phschafft>
but you could also do ethernet over SCSI, which I used.
<OscarL>
now we wait for people with merge rights :-)
Halian has quit [Quit: I'll be back.]
<phschafft>
;)
xet7 has joined #haiku
mmu_man has quit [Ping timeout: 480 seconds]
<OscarL>
funny when a project tells you: "Deprecated Feature: Using arbitrary fields (format_note) for format sorting is deprecated and may be removed in a future version", when they don't yet offer a non-deprecated alternative.
<OscarL>
that "abi3" is a giveway that the .so is a Python extension.
<Begasus[m]>
it comes included, didn't change anything there :)
<OscarL>
so my gut feeling is that it doesn't belongs under "lib/". But again, maybe it is something I'm just not familiar enough with.
<Begasus[m]>
it's using ${LIB_INSTALL_DIR} for that, so I guess that's the purpose?
<Begasus[m]>
in Arch they are also in usr/lib
<OscarL>
I guess is just the naming that is throwing me off.
<OscarL>
more likely to be "Qt extensions to be able to interface with python", than being proper python extensions (as the Shiboken.abi3.so under vendor-packages/shiboken6/).
<OscarL>
like... the latter is the python side of the interface/bindings, while the other .so under lib/ are the "qt/pyside" side of things.
<Begasus[m]>
the Qt ones for PySide6 are under /boot/system/lib/python3.10/vendor-packages/PySide6
<OscarL>
yeah, nevermind me. It is just me not having a good idea of how these pieces work together.
<Begasus[m]>
too early in the morning to wrap my head around this :D
<Begasus[m]>
not releasing it any time soon anyway (probably also needs the archive for 6.7.2 for that) :)
<OscarL>
"pkman search -r libpython3.9" give no results (on 64 bits). progress! :-)
<Begasus[m]>
yes! :D
<OscarL>
"pkgman search -r cmd:python3.9 | grep -v _python" also no results. So only users of 3.9 must be BUILD_REQUIRES.
<OscarL>
"nodejs16" and "qgis"
<OscarL>
darn "fife" still using: "-DPYTHON_SITE_PACKAGES=$prefix/lib/python3.9/vendor-packages \" :-)
<Begasus[m]>
nodejs16 should kinda be depricated
<Begasus[m]>
guess an update there would be at hand, they are pretty fast on releases
<OscarL>
our Iceweasel port was still using it at build time. that's why I opened an issue suggesting them to switch to node20 or something :-) (if possible)
<OscarL>
seems Iceweasel 128 used nodejs16, but 137 already uses nodejs20
<OscarL>
so maybe we should drop nodejs16 after all.
erysdren has quit [Quit: Konversation terminated!]
<Begasus[m]>
will add it in my "todo" list to check it out :)
<OscarL>
at least on 64 bits, nothing uses it at runtime ("pkgman search -r nodejs16" only shows the nodejs16_devel package), and "inrecipe nodejs16" only shows iceweasel-128 :-)
<Begasus[m]>
yeah, seem only /Opslag/haikuports/www-client/iceweasel/iceweasel-128.5.0.recipe:60: nodejs16
<Begasus[m]>
don't have it installed also here
<OscarL>
nim might need a rebuild, as it ask for cmd:node >= 16
<Begasus[m]>
eeps
<OscarL>
or maybe not even that.... once nodejs16 gets removed...
<OscarL>
pkgman/packagekit should find the provide from cmd:node == 20 as valid.
<OscarL>
(I hope :-D)
<Begasus[m]>
nim only has it in BUILD_REQUIRES
<OscarL>
and only for docs generation
<Begasus[m]>
installing nim doesn't pull it
<Begasus[m]>
yeah
<OscarL>
which might not even be needed (at least many projects also offer "pre-built" docs)
<Begasus[m]>
23.11.0 :P
<OscarL>
so.... nuking nodejs16 seems pretty safe (famous last words)
<Begasus[m]>
heh
tuaris has quit [Quit: tuaris]
<Begasus[m]>
oh bugger, not a small patchset there too :/
<Begasus[m]>
still not as big as the one from wine :P
<OscarL>
Always good when "past you" was nice enough to add docs and a "--help" option on "random" scripts you forget you wrote already :-D
<OscarL>
can't they be installed side by side as Pythons can?
Xe has quit [Ping timeout: 480 seconds]
<Begasus[m]>
cmd:nodejs is the same for both
<Begasus[m]>
but if possible would rather drop the old one
<Begasus[m]>
bah ... error: sha1 information is lacking or useless (common.gypi).
<Begasus[m]>
biab ... :)
Xe has joined #haiku
freddietilley has joined #haiku
<jessicah>
OscarL: did the media addon bug resurface for you at all?
<OscarL>
not so far jessicah.
<OscarL>
I should test also on the slow Atom N450 netbook, just to be sure it helps there too.
<jessicah>
hmm, because I'm not sure it's actually the correct fix now
<Begasus[m]>
back to ground zero? :)
<OscarL>
the issue was so bad for me that I just ended up blacklisting the hda driver on most of my installs...
<OscarL>
and after adding the modifed addon, tested on this Phenom... and on VirtualBox and VMware. no crashes there.
<jessicah>
Begasus[m]: haha, yeah, it's a weird intricate maze of timestamps
<OscarL>
let's see what the N450 netbook does. (/me goes to make some coffee, and to find the power brick for the netbook)
<jessicah>
like it did seem to get rid of the bug here too, but additional tracing seems to indicate that it wasn't the cause, which is just more weird
<OscarL>
(darn desktop PC is falling appart, only 2 USB ports seem to still work, sigh)
<OscarL>
darn netbook decided to not boot with SMP enabled again, lol. it just likes to troll me.
<OscarL>
heh, have 3 media_addon_server.[].report file on its desktop... albeit in this boot I didn't get the crash.
AlaskanEmily has quit [Remote host closed the connection]
mmu_man has joined #haiku
zelectric has quit [Quit: ]
<OscarL>
Mmm, was able to boot with SMP enabled, and no crash with the original hmulti_audio.media_addon. Hate this kind of bugs :-(
<Begasus[m]>
maybe I should fire up qemu for checking this thing on 32bit :P
<Begasus[m]>
think it's faster then the one on bare metal atm :)
<OscarL>
(netbook is running hrev58289 and not beta5, from where I remember having many crashes :-/)
<Begasus[m]>
spooky there :D
<OscarL>
trying VirtualBox beta5 with original addon.
<OscarL>
works too. what the heck?
<Begasus[m]>
hehe
<OscarL>
this was giving me consistent crashes on boot :-/ (but can't remember if that before or after I got the SSD).
* OscarL
plays Weird Al's "White and Nerdy" on the netbook to "stress test" :-D
<jessicah>
haha
<OscarL>
darn. Even booted my previous install from HDD (originally beta5, now hrev58387) in VBox... no crash with the original addon. (and have 9 reports of media_addon_server crashes date Sep-2024 to Nov-2024)
<OscarL>
*errr... read wrong column... date range was: Aug-to-Oct 2024
<Begasus[m]>
bugger, need to make a patch(*) for qt6_base
<OscarL>
Same thing when I try to chase Tracker crashes with libroot_debug... bugs are shy and do not appear when you're looking :-(
<OscarL>
want to do some actual work... Tracker crashes left and right, heh.
<Begasus[m]>
it's like going to the dentist ;)
<OscarL>
not even in 32 bits I get the error now :-/
HaikuUser has joined #haiku
HaikuUser is now known as Begas_
<Begasus[m]>
about to loose focus :P
<Begasus[m]>
3 laptops open atm :)
<OscarL>
oldish beta5 on the netbook... no crash. this is nuts.
<Begasus[m]>
oldish? :P
<OscarL>
+90 instead of +129
<Begasus[m]>
errr ... yep, slacker! :P
mmu_man has quit [Ping timeout: 480 seconds]
MisthaLu has quit [Quit: Leaving]
Begas_ has quit [Quit: Vision[]: i've been blurred!]
<Begasus[m]>
sed -i 's,${_IMPORT_PREFIX}/lib/libQt6ExampleIcons.a',$developDir/lib/libQt6ExampleIcons.a (guess this should be $developLibDir instead of $developDir/lib)
<Begasus[m]>
now it mentions lib/x86/... on 32 bit, which is wrong also according to the above ...
<Begasus>
phschafft, kid in 1997/1998, that's atleast 1 decade to me :)
<Begasus>
to my age* :)
<Begasus>
4032*
_-Caleb-_ has left #haiku [#haiku]
_-Caleb-_ has joined #haiku
jack-sparrow has joined #haiku
<jack-sparrow>
be back
<Begasus>
wb :)
erysdren has joined #haiku
<Peppersawce>
@Begasus, I tried disabling the line that's making AssaultCube's build fail and it works fine here, do you think it's worth it to push this change?
<Begasus>
if it doesn't brake, go for it, add some note on why it's done that way though
<Begasus>
Peppersawce, there are already a few examples on pthread_setname_np in the patches :)
<Begasus>
I could merge this as is, or wait for another patch, up to you :)
<roadroller>
i install chocolate doom but it dont work. how can i play it? it says "no iwad file found"
<Peppersawce>
@Begasus, imo not worth working on it more tbh, it's a temp fix and will be rolled back
<Peppersawce>
Also, it's part of debug stuff which afaict from the code shouldn't work on Haiku in the first place
<Peppersawce>
@roadroller, check the package description in HaikuDepot, that one should explain where to put the wad files so chocodoom sees them
<Peppersawce>
Alternatively there's installable packs for stuff like Freedoom and Chex Quest
<Peppersawce>
Note that chocodoom doesn't ship with any wad by default, you need to provide the wad files yourself (or download one of the packages I mentioned)
<Begasus>
ok, np, will merge then :)
roadroller has quit [Ping timeout: 480 seconds]
<Peppersawce>
Nice :D
<nekobot>
• Peppersawce (d50eb5ee): AssaultCube: another attempt at buildmaster fix (#12226)
<Peppersawce>
And then you can flash it using some various tools, like BalenaEtcher on Windows or... dd on Linux
<Peppersawce>
Or even dd from Haiku itself?
<Habbie>
ohhh. haiku's stage1 and stage2 boot loaders cannot be modified separately. stage2 relies on some of the functions at expected offsets in stage1
<Habbie>
i spent some time being puzzled yesterday by "all i did was add some dead code in the middle of stage1 and now nothing works"
<jack-sparrow>
oh so bad :D
<Habbie>
when i say 'stage2' i mean the second 512 bytes of stage1, but stage1 loads that from disk separately
<jack-sparrow>
it' s great
<jack-sparrow>
very well
<jack-sparrow>
but if there are some code between stage 1 and stage 2 may be do problem
<jack-sparrow>
stage 1 is the hybrid kernel ?
<Habbie>
no, the kernel is like stage 20
<jack-sparrow>
:D
<jack-sparrow>
and stage 2 ?
<Habbie>
stage 2 knows just enough BFS to load something from disk
<jack-sparrow>
ok great
Peppersawce has quit [Quit: Vision[]: i've been blurred!]
Peppersawce has joined #haiku
bbjimmy has quit [Quit: Vision[]: i've been blurred!]
bbjimmy has joined #haiku
jack-sparrow has quit [Ping timeout: 480 seconds]
<Habbie>
wow, stage2 has -zero- bytes to spare
gouchi has joined #haiku
gouchi has quit [Remote host closed the connection]
deneel has quit [Quit: deneel]
erysdren has quit [Quit: Konversation terminated!]
<nekobot>
[haiku/haiku] 6259a27b726a - kernel/x86: Invoke debug_double_fault on x86_64.
<nekobot>
[haiku/haiku] 10eea8dfae01 - kernel/debug: Fix handling of sInvokeCommandLevel.
<Habbie>
hey i have email
<Habbie>
which says what i was thinking
<Habbie>
:)
<waddlesplash>
:)
<Habbie>
(ticket 14082)
<waddlesplash>
yeah
<Habbie>
but i'm too busy porting stage1.nasm to DOS
<Habbie>
:D
<waddlesplash>
the changes on 32-bit x86 may affect things also
<waddlesplash>
to DOS? why? lol
<Habbie>
so i can DEBUG.COM it
<Habbie>
on this chromebook
<Habbie>
whenever i manage to get stage1 to not error, the chromebook reboots. I can imagine many reasons, but i'd rather actually know why
<Habbie>
i've already managed to run stage1.bin manually, but given i'm not actually in a boot environment, i can add way more debugging output
<waddlesplash>
interesting
<waddlesplash>
are you sure it's not rebooting inside stage2 or later?
<waddlesplash>
do you have serial info?
<Habbie>
i am just about to be convinced the reboot is in stage2, but making stage1 easier to run from DOS might allow me to single step into haiku_loader (that's what you mean by stage2? or 3) to figure it out, unless the reboot after the switch from real mode
<Habbie>
i do not have serial
<waddlesplash>
that's unfortunate, because with serial it's easy to immediately tell if the reboot is in stage2 or later
<Habbie>
anyway, some hours in i realised that the second half of stage1 (loaded by the first half) depends on compiled-in function offsets in the first half
<Habbie>
and now i'm just trying to make my life easier by having both halves of stage1 in one dos binary
<Habbie>
waddlesplash, i haven't looked at stage2 at all - does it write to serial early?
<waddlesplash>
yes
<Habbie>
nice
<Habbie>
patching it to do bios text writes, and waiting for a key press, might be useful here then
<Habbie>
yeah, i think i have the parts to make that
<Habbie>
but i haven't yet
<Habbie>
my chromebook is currently still write protected
<Habbie>
i'm not opposed to unprotecting it but scientifically i feel i shouldn't have to
<Habbie>
but serial logging is an interesting motivator - i read the suzyq would allow me to un-WP it, and i was wondering today if it gave me serial, just didn't look yet
<waddlesplash>
it appears that it does have serial
<Habbie>
yes
<Habbie>
your url answers that addon question that came to me today :)
<Habbie>
incidentally i think i also have the parts to add serial to the AMD box that presumably suffers from the faults, but until now we suspected it would not help
<waddlesplash>
there is an ever-so-slim chance it might
<Habbie>
ack
<Habbie>
it is on my list, just not in a defined position right now
<waddlesplash>
if we are getting into KDL and something weird happens before the screen gets refreshed it might be interesting
<waddlesplash>
but seeing as I don't see anyone reporting a "white flash" before the reboot, maybe not
<waddlesplash>
this hacks up the BIOS loader to switch to using a "video" console very early
<waddlesplash>
... actually I might be able to make it switch even earlier than that
<waddlesplash>
eh, probably not worthwhile, in all likelihood
<Habbie>
ah, that patch is slightly longer than expected
<Habbie>
thanks
<Habbie>
i'll report back :)
<waddlesplash>
I also had to make some other fixes to the bootloader which aren't hacks
<waddlesplash>
to make it work
<waddlesplash>
that's what I committed in hrev58828
<Habbie>
ah so the patch sits on top of 58828?
<waddlesplash>
yes
<Habbie>
got it
<Peppersawce>
Hey, do these patches mean I could actually read the bootloader's output when it hangs on my pc?
<Peppersawce>
Without serial
<Habbie>
hangs how?
<waddlesplash>
you should already be able to do that with "onscreen debug out"
<Peppersawce>
No lights up
<waddlesplash>
that means the bootloader started and initialized the video mode
<waddlesplash>
so, get into the bootloader menu and enable onscreen debug out
_-Caleb-_ has left #haiku [#haiku]
_-Caleb-_ has joined #haiku
<Peppersawce>
Hm, that never worked for me
<waddlesplash>
on recent nightlies (last few months that is, can't remember when I made the change exactly), the kernel can initialize the debug framebuffer a lot earlier
<waddlesplash>
this turned a lot of the "hangs on boot, nothing lit up" into visible KDLs
<waddlesplash>
or if not that, at least something in the onscreen log, when previously nothing was displayed
<Peppersawce>
I swear I tried checking if it was possible but i probably missed something
<Peppersawce>
(with a recent bootloader)
<waddlesplash>
but also a lot of the "no icons light up" also got fixed in recent months
<waddlesplash>
Peppersawce: it's the kernel, not the bootloader, in this case
<Habbie>
waddlesplash, as always, thanks for indulging me. as mentioned, EFI would make my life simpler, but i somewhat hope that my/our efforts will aid some future problem for a less stubborn user who also has a problem
<Peppersawce>
Eh... yeah, I'm still a bit confused about it :D
<waddlesplash>
Peppersawce there are some things that can go wrong once the icons are displayed inside the bootloader, but not a lot; most of the problems after that point can happen in the kernel
<waddlesplash>
but the kernel early init has a lot of ways it can go wrong
<waddlesplash>
and if that happens the first icon won't be lit
<waddlesplash>
the new changes here from a few months ago make it much more likely we will get visible information from the kernel when something goes wrong
<Peppersawce>
Hope I remember all this next time it happens
<Peppersawce>
It is pretty random though, most of the time it boots fine
<waddlesplash>
if you are on a nightly build then there isn't anything you need to do to get KDL to work in this sage
<waddlesplash>
stage
<waddlesplash>
it will now "just work" hopefully
<waddlesplash>
onscreen debug output, yes, that's a bootloader option
<waddlesplash>
Peppersawce: oh, these changes are 64-bit only FWIW
<waddlesplash>
but most people are on 64bit anyway
<Peppersawce>
That's ok, I'm on 64bit :)
<Peppersawce>
Onscreen debug is actually pretty hard, for one I have to be fast enough to spam SHIFT, then I have to roll the dice and hope it hangs lmao
<waddlesplash>
Habbie: ok, I just tested some more with that patch, it doesn't seem to work for printing dprintfs to the screen lol. The menu does work in this state however
<waddlesplash>
Peppersawce: on BIOS loader, you can hold SHIFT starting at or just after your BIOS POSTs
<waddlesplash>
so before the Haiku loader even starts
<waddlesplash>
Habbie: no
<Peppersawce>
Good to know
<waddlesplash>
Habbie: this patch hacks up the loader to switch to VESA immediately and use its own console implementation to output text to the framebuffer
OscarL has quit [Remote host closed the connection]
<Habbie>
oh like that
<Habbie>
that reminds me, and i could check, but i haven't - do you expect certain VESA modes to be available or do you do the whole "see what the BIOS got" dance?
<waddlesplash>
the latter
<Habbie>
ok cool
<waddlesplash>
and we try to read EDID too
<waddlesplash>
the loader is pretty advanced here
<Habbie>
that rules out one reason on my long list of reasons for failure
<Habbie>
(potential reasons)
<Habbie>
my seabios offers 640x480-1024x768 in, iirc, 0x141-0x144
<Peppersawce>
"my long list of reasons for failure" is such a line... and a mood
<Habbie>
:)
<Peppersawce>
Too bad it's too long for a band name
<Habbie>
nah
<Peppersawce>
Maybe it's fine for an album title tho
<waddlesplash>
Habbie: ok, that patch fixes onscreen debug prints before the menu appears
<Habbie>
cool
<waddlesplash>
you may however also want to open that same file, video_text_console.cpp, and where it has "already handled above" for \n, add: "spin(500 * 1000);"
<waddlesplash>
this adds a half-second delay every \n
<Habbie>
ok
<waddlesplash>
the interactive menu never prints \n so it won't slow that down
<waddlesplash>
just the log
<waddlesplash>
ah, actually it might
<waddlesplash>
well, it doesn't print it on screen refreshes it appears, those are fast