#nosh — Public Fediverse posts
Live and recent posts from across the Fediverse tagged #nosh, aggregated by home.social.
-
I'm not the only person to provide a full off-line browsable HTML guide to my softwares in the box, also. (-:
In case anyone else hits it: The version of xgettext in #NetBSD 10.1 is old enough (0.16) that it breaks the #WatanabeShell build. You need the one that is in pkgsrc (0.22).
-
I'm not the only person to provide a full off-line browsable HTML guide to my softwares in the box, also. (-:
In case anyone else hits it: The version of xgettext in #NetBSD 10.1 is old enough (0.16) that it breaks the #WatanabeShell build. You need the one that is in pkgsrc (0.22).
-
I'm not the only person to provide a full off-line browsable HTML guide to my softwares in the box, also. (-:
In case anyone else hits it: The version of xgettext in #NetBSD 10.1 is old enough (0.16) that it breaks the #WatanabeShell build. You need the one that is in pkgsrc (0.22).
-
I'm not the only person to provide a full off-line browsable HTML guide to my softwares in the box, also. (-:
In case anyone else hits it: The version of xgettext in #NetBSD 10.1 is old enough (0.16) that it breaks the #WatanabeShell build. You need the one that is in pkgsrc (0.22).
-
I'm not the only person to provide a full off-line browsable HTML guide to my softwares in the box, also. (-:
In case anyone else hits it: The version of xgettext in #NetBSD 10.1 is old enough (0.16) that it breaks the #WatanabeShell build. You need the one that is in pkgsrc (0.22).
-
https://www.europesays.com/africa/369621/ Discover the top 4 Crypto Platforms in Nigeria in 2026 #BestCryptoTradingServices #BestRatesForCryptoTrading #Bitcoin #coincola #CryptoPlatform #CryptoPlatformsNigeria #kucoin #Nigeria #nosh #ReliableCryptoPlatform #Top4CryptoPlatforms #TopCryptoPlatform #UseNosh #YellowCard
-
Does /dev/coreboot-console change at runtime? I added a service for it to the #nosh collection, analogous to the collection's dmesg service that spits out /dev/dmesg.boot, which was the work of about 10 minutes; but I'm wondering whether it's even worth it.
-
Does /dev/coreboot-console change at runtime? I added a service for it to the #nosh collection, analogous to the collection's dmesg service that spits out /dev/dmesg.boot, which was the work of about 10 minutes; but I'm wondering whether it's even worth it.
-
Does /dev/coreboot-console change at runtime? I added a service for it to the #nosh collection, analogous to the collection's dmesg service that spits out /dev/dmesg.boot, which was the work of about 10 minutes; but I'm wondering whether it's even worth it.
-
Does /dev/coreboot-console change at runtime? I added a service for it to the #nosh collection, analogous to the collection's dmesg service that spits out /dev/dmesg.boot, which was the work of about 10 minutes; but I'm wondering whether it's even worth it.
-
Does /dev/coreboot-console change at runtime? I added a service for it to the #nosh collection, analogous to the collection's dmesg service that spits out /dev/dmesg.boot, which was the work of about 10 minutes; but I'm wondering whether it's even worth it.
-
Looking at the blurb afresh, I see that it still uses the login program to login.
That isn't necessary nowadays. One thing that I later added to the toolset was a replacement program that assumed that one had at least a 1970s video terminal with a repositionable cursor, and draws a full-screen TUI with the user/password prompts as text entry fields.
http://jdebp.info/Softwares/nosh/guide/commands/login-envuidgid.xml
I assume that the old paper terminal login style works better for the #brltty case, though.
-
Looking at the blurb afresh, I see that it still uses the login program to login.
That isn't necessary nowadays. One thing that I later added to the toolset was a replacement program that assumed that one had at least a 1970s video terminal with a repositionable cursor, and draws a full-screen TUI with the user/password prompts as text entry fields.
http://jdebp.info/Softwares/nosh/guide/commands/login-envuidgid.xml
I assume that the old paper terminal login style works better for the #brltty case, though.
-
Looking at the blurb afresh, I see that it still uses the login program to login.
That isn't necessary nowadays. One thing that I later added to the toolset was a replacement program that assumed that one had at least a 1970s video terminal with a repositionable cursor, and draws a full-screen TUI with the user/password prompts as text entry fields.
http://jdebp.info/Softwares/nosh/guide/commands/login-envuidgid.xml
I assume that the old paper terminal login style works better for the #brltty case, though.
-
Looking at the blurb afresh, I see that it still uses the login program to login.
That isn't necessary nowadays. One thing that I later added to the toolset was a replacement program that assumed that one had at least a 1970s video terminal with a repositionable cursor, and draws a full-screen TUI with the user/password prompts as text entry fields.
http://jdebp.info/Softwares/nosh/guide/commands/login-envuidgid.xml
I assume that the old paper terminal login style works better for the #brltty case, though.
-
Looking at the blurb afresh, I see that it still uses the login program to login.
That isn't necessary nowadays. One thing that I later added to the toolset was a replacement program that assumed that one had at least a 1970s video terminal with a repositionable cursor, and draws a full-screen TUI with the user/password prompts as text entry fields.
http://jdebp.info/Softwares/nosh/guide/commands/login-envuidgid.xml
I assume that the old paper terminal login style works better for the #brltty case, though.
-
For what it's worth, I've long since been providing a terminal emulator, that runs on both #FreeBSD and #NetBSD, that can also optionally provide a Linux-format vcsa file, a format that #brltty already understands and can read.
http://jdebp.info/Softwares/nosh/brltty.html
http://jdebp.info/Softwares/nosh/guide/commands/console-terminal-emulator.xml
I wrote up that blurb in 2014, and it still does that today, although I did in 2015 make vcsa file generation a non-default option, as there's also a better full Unicode display file available.
-
For what it's worth, I've long since been providing a terminal emulator, that runs on both #FreeBSD and #NetBSD, that can also optionally provide a Linux-format vcsa file, a format that #brltty already understands and can read.
http://jdebp.info/Softwares/nosh/brltty.html
http://jdebp.info/Softwares/nosh/guide/commands/console-terminal-emulator.xml
I wrote up that blurb in 2014, and it still does that today, although I did in 2015 make vcsa file generation a non-default option, as there's also a better full Unicode display file available.
-
For what it's worth, I've long since been providing a terminal emulator, that runs on both #FreeBSD and #NetBSD, that can also optionally provide a Linux-format vcsa file, a format that #brltty already understands and can read.
http://jdebp.info/Softwares/nosh/brltty.html
http://jdebp.info/Softwares/nosh/guide/commands/console-terminal-emulator.xml
I wrote up that blurb in 2014, and it still does that today, although I did in 2015 make vcsa file generation a non-default option, as there's also a better full Unicode display file available.
-
For what it's worth, I've long since been providing a terminal emulator, that runs on both #FreeBSD and #NetBSD, that can also optionally provide a Linux-format vcsa file, a format that #brltty already understands and can read.
http://jdebp.info/Softwares/nosh/brltty.html
http://jdebp.info/Softwares/nosh/guide/commands/console-terminal-emulator.xml
I wrote up that blurb in 2014, and it still does that today, although I did in 2015 make vcsa file generation a non-default option, as there's also a better full Unicode display file available.
-
For what it's worth, I've long since been providing a terminal emulator, that runs on both #FreeBSD and #NetBSD, that can also optionally provide a Linux-format vcsa file, a format that #brltty already understands and can read.
http://jdebp.info/Softwares/nosh/brltty.html
http://jdebp.info/Softwares/nosh/guide/commands/console-terminal-emulator.xml
I wrote up that blurb in 2014, and it still does that today, although I did in 2015 make vcsa file generation a non-default option, as there's also a better full Unicode display file available.
-
That could very well be your problem. Something is waiting for #DesktopBus, and it's taking its time for the per-user broker to come up.
D-Bus is a bit fragile. I had to go through all of this stuff for per-user service management with the #nosh toolset, and there are many ways in which the D-Bus mechanisms can break.
A few ways were because originally the design was that the first client forked the broker process. Not good when the client's resource limited.
-
That could very well be your problem. Something is waiting for #DesktopBus, and it's taking its time for the per-user broker to come up.
D-Bus is a bit fragile. I had to go through all of this stuff for per-user service management with the #nosh toolset, and there are many ways in which the D-Bus mechanisms can break.
A few ways were because originally the design was that the first client forked the broker process. Not good when the client's resource limited.
-
That could very well be your problem. Something is waiting for #DesktopBus, and it's taking its time for the per-user broker to come up.
D-Bus is a bit fragile. I had to go through all of this stuff for per-user service management with the #nosh toolset, and there are many ways in which the D-Bus mechanisms can break.
A few ways were because originally the design was that the first client forked the broker process. Not good when the client's resource limited.
-
That could very well be your problem. Something is waiting for #DesktopBus, and it's taking its time for the per-user broker to come up.
D-Bus is a bit fragile. I had to go through all of this stuff for per-user service management with the #nosh toolset, and there are many ways in which the D-Bus mechanisms can break.
A few ways were because originally the design was that the first client forked the broker process. Not good when the client's resource limited.
-
That could very well be your problem. Something is waiting for #DesktopBus, and it's taking its time for the per-user broker to come up.
D-Bus is a bit fragile. I had to go through all of this stuff for per-user service management with the #nosh toolset, and there are many ways in which the D-Bus mechanisms can break.
A few ways were because originally the design was that the first client forked the broker process. Not good when the client's resource limited.
-
It's food for thought, too. All this fuss made about cat, repeated to this day in some quarters, and of the three things explicitly pointed out as wrong with what Berkeley did, only a tool to do one of them, vis(1), was ever written in 43 years.
The ironic cherry on top is that the only operating systems that come with vis out of the box are the BSDs.
-
It's food for thought, too. All this fuss made about cat, repeated to this day in some quarters, and of the three things explicitly pointed out as wrong with what Berkeley did, only a tool to do one of them, vis(1), was ever written in 43 years.
The ironic cherry on top is that the only operating systems that come with vis out of the box are the BSDs.
-
It's food for thought, too. All this fuss made about cat, repeated to this day in some quarters, and of the three things explicitly pointed out as wrong with what Berkeley did, only a tool to do one of them, vis(1), was ever written in 43 years.
The ironic cherry on top is that the only operating systems that come with vis out of the box are the BSDs.
-
It's food for thought, too. All this fuss made about cat, repeated to this day in some quarters, and of the three things explicitly pointed out as wrong with what Berkeley did, only a tool to do one of them, vis(1), was ever written in 43 years.
The ironic cherry on top is that the only operating systems that come with vis out of the box are the BSDs.
-
It's food for thought, too. All this fuss made about cat, repeated to this day in some quarters, and of the three things explicitly pointed out as wrong with what Berkeley did, only a tool to do one of them, vis(1), was ever written in 43 years.
The ironic cherry on top is that the only operating systems that come with vis out of the box are the BSDs.
-
The 'cat -v considered harmful folks' (Kernighan and Pike) invented vis(1).
> The preferred approach in this case is a separate program that deals with non-printable characters. We called ours vis […] because its job is to make things visible.
I suspect that they would approve of sqz(1) likewise abstracted from cat -s, because they also said
> cat isn’t […] for compressing multiple blank lines […] it’s for concatenating files.
-
The 'cat -v considered harmful folks' (Kernighan and Pike) invented vis(1).
> The preferred approach in this case is a separate program that deals with non-printable characters. We called ours vis […] because its job is to make things visible.
I suspect that they would approve of sqz(1) likewise abstracted from cat -s, because they also said
> cat isn’t […] for compressing multiple blank lines […] it’s for concatenating files.
-
The 'cat -v considered harmful folks' (Kernighan and Pike) invented vis(1).
> The preferred approach in this case is a separate program that deals with non-printable characters. We called ours vis […] because its job is to make things visible.
I suspect that they would approve of sqz(1) likewise abstracted from cat -s, because they also said
> cat isn’t […] for compressing multiple blank lines […] it’s for concatenating files.
-
The 'cat -v considered harmful folks' (Kernighan and Pike) invented vis(1).
> The preferred approach in this case is a separate program that deals with non-printable characters. We called ours vis […] because its job is to make things visible.
I suspect that they would approve of sqz(1) likewise abstracted from cat -s, because they also said
> cat isn’t […] for compressing multiple blank lines […] it’s for concatenating files.
-
The 'cat -v considered harmful folks' (Kernighan and Pike) invented vis(1).
> The preferred approach in this case is a separate program that deals with non-printable characters. We called ours vis […] because its job is to make things visible.
I suspect that they would approve of sqz(1) likewise abstracted from cat -s, because they also said
> cat isn’t […] for compressing multiple blank lines […] it’s for concatenating files.
-
Well since vis(1) came about because of cat -v, it seems that there should be a sqz(1) because of cat -s .
-
Well since vis(1) came about because of cat -v, it seems that there should be a sqz(1) because of cat -s .
-
Well since vis(1) came about because of cat -v, it seems that there should be a sqz(1) because of cat -s .
-
Well since vis(1) came about because of cat -v, it seems that there should be a sqz(1) because of cat -s .
-
Well since vis(1) came about because of cat -v, it seems that there should be a sqz(1) because of cat -s .
-
As you can see, @rl_dane has me wondering whether anyone has ever written a sqz(1) #Unix #TextProcessing tool, to go alongside vis(1).
https://tty0.social/@JdeBP/116834743954481512
I am tempted to just quickly knock one together and put it into the #nosh toolset.
-
As you can see, @rl_dane has me wondering whether anyone has ever written a sqz(1) #Unix #TextProcessing tool, to go alongside vis(1).
https://tty0.social/@JdeBP/116834743954481512
I am tempted to just quickly knock one together and put it into the #nosh toolset.
-
As you can see, @rl_dane has me wondering whether anyone has ever written a sqz(1) #Unix #TextProcessing tool, to go alongside vis(1).
https://tty0.social/@JdeBP/116834743954481512
I am tempted to just quickly knock one together and put it into the #nosh toolset.
-
As you can see, @rl_dane has me wondering whether anyone has ever written a sqz(1) #Unix #TextProcessing tool, to go alongside vis(1).
https://tty0.social/@JdeBP/116834743954481512
I am tempted to just quickly knock one together and put it into the #nosh toolset.
-
As you can see, @rl_dane has me wondering whether anyone has ever written a sqz(1) #Unix #TextProcessing tool, to go alongside vis(1).
https://tty0.social/@JdeBP/116834743954481512
I am tempted to just quickly knock one together and put it into the #nosh toolset.
-
When you view manual pages on a video terminal, the -s ('squeeze') option to the final $PAGER in the pipeline does this. You'll be surprised at how many blank lines there really are in manuals.
less, (BSD) more, most, and (my) console-tty37-viewer all have this option.
Given that, it's an of course moment, with a nod to the people who think that this should no more be a part of cat than vis(1) is, that cat has a squeeze option too.
-
When you view manual pages on a video terminal, the -s ('squeeze') option to the final $PAGER in the pipeline does this. You'll be surprised at how many blank lines there really are in manuals.
less, (BSD) more, most, and (my) console-tty37-viewer all have this option.
Given that, it's an of course moment, with a nod to the people who think that this should no more be a part of cat than vis(1) is, that cat has a squeeze option too.
-
When you view manual pages on a video terminal, the -s ('squeeze') option to the final $PAGER in the pipeline does this. You'll be surprised at how many blank lines there really are in manuals.
less, (BSD) more, most, and (my) console-tty37-viewer all have this option.
Given that, it's an of course moment, with a nod to the people who think that this should no more be a part of cat than vis(1) is, that cat has a squeeze option too.
-
When you view manual pages on a video terminal, the -s ('squeeze') option to the final $PAGER in the pipeline does this. You'll be surprised at how many blank lines there really are in manuals.
less, (BSD) more, most, and (my) console-tty37-viewer all have this option.
Given that, it's an of course moment, with a nod to the people who think that this should no more be a part of cat than vis(1) is, that cat has a squeeze option too.
-
When you view manual pages on a video terminal, the -s ('squeeze') option to the final $PAGER in the pipeline does this. You'll be surprised at how many blank lines there really are in manuals.
less, (BSD) more, most, and (my) console-tty37-viewer all have this option.
Given that, it's an of course moment, with a nod to the people who think that this should no more be a part of cat than vis(1) is, that cat has a squeeze option too.
-
https://www.europesays.com/iran/172035/ Years After a Boycott Fight, Ben & Jerry’s Israel Debuts a Flavor Celebrating Israeli Resilience | Culture #Culture #Israel #JewishTelegraphicAgency #nosh
-
https://www.europesays.com/iran/154561/ Former Michiganders Share How Food Selection and Prep Differ in Israel | Culture #Culture #Israel #nosh
-
【番外編】ミニキングスリーグ開幕！ということで、ムラッシュFC nosh（ナッシュ）語呂もいい 本当スポンサードに感謝だよなぁ・・おいしそう。｜水野五郞 @mizugoro0489 https://note.com/mizugoro0489/n/n8e1dad87bbf7?sub_rt=share_pb
#ムラッシュFC
#nosh
#キングスリーグ -
https://mizugoro0489.jp/mizunogoro-782/
【番外編】ミニキングスリーグ開幕！ということで、
ムラッシュFC nosh（ナッシュ）語呂もいい
本当スポンサードに感謝だよなぁ・・おいしそう。
#ムラッシュFC
#nosh
#キングスリーグ -
【nosh】ついに広告衣装実装！気になったお弁当の実食＆ランキング！【アキロゼ/ホロライブ】
https://www.youtube.com/watch?v=dhRh7BuHUbA#youtube_AkiRosenthal #Vtuber #virtual #バーチャルyoutuber #ホロライブ #hololive #anime #Nosh #食レポ
-
Since I was visiting the 'daemontools' account on #GitHub, I took a look at what the people who mistakenly thought that it was someone actually involved, have done.
Not much, fortunately.
One wheel reinvention that didn't even look at Bruce Guenter's daemontools-encore.
Only one thing worth following up on, in 13 years:
https://github.com/daemontools/daemontools/issues/8
The bugfix will be in #djbwares version 13 when it comes out. As noted, neither @ska's nor my #nosh reimplementations have this bug.
-
Since I was visiting the 'daemontools' account on #GitHub, I took a look at what the people who mistakenly thought that it was someone actually involved, have done.
Not much, fortunately.
One wheel reinvention that didn't even look at Bruce Guenter's daemontools-encore.
Only one thing worth following up on, in 13 years:
https://github.com/daemontools/daemontools/issues/8
The bugfix will be in #djbwares version 13 when it comes out. As noted, neither @ska's nor my #nosh reimplementations have this bug.
-
Since I was visiting the 'daemontools' account on #GitHub, I took a look at what the people who mistakenly thought that it was someone actually involved, have done.
Not much, fortunately.
One wheel reinvention that didn't even look at Bruce Guenter's daemontools-encore.
Only one thing worth following up on, in 13 years:
https://github.com/daemontools/daemontools/issues/8
The bugfix will be in #djbwares version 13 when it comes out. As noted, neither @ska's nor my #nosh reimplementations have this bug.
-
Since I was visiting the 'daemontools' account on #GitHub, I took a look at what the people who mistakenly thought that it was someone actually involved, have done.
Not much, fortunately.
One wheel reinvention that didn't even look at Bruce Guenter's daemontools-encore.
Only one thing worth following up on, in 13 years:
https://github.com/daemontools/daemontools/issues/8
The bugfix will be in #djbwares version 13 when it comes out. As noted, neither @ska's nor my #nosh reimplementations have this bug.