~pixelherodev

~pixelherodev/knightos

Last active 2 years ago

~pixelherodev/cyclopropatriene-devel

Last active 3 years ago

~pixelherodev/cyclopropatriene-announce

Last active 3 years ago

~pixelherodev/public-inbox

Last active 3 years ago

~pixelherodev/zany80-discuss

Last active 3 years ago

~pixelherodev/zany80-devel

Last active 3 years ago

~pixelherodev/zany80-announce

Last active 3 years ago

~pixelherodev/coyote-discuss

Last active 3 years ago

~pixelherodev/coyote-devel

Last active 3 years ago

~pixelherodev/coyote-announce

Last active 3 years ago
View more

Recent activity

[PATCH] test git send email on new machine 5 months ago

From Noam Preil to ~sircmpwn/email-test-drive

---
 no | 1 +
 1 file changed, 1 insertion(+)
 create mode 100644 no

diff --git a/no b/no
new file mode 100644
index 0000000..6d0ecfd
--- /dev/null
+++ b/no
@@ -0,0 +1 @@
I'm about to try git send-email
-- 
2.43.0
[message trimmed]

Re: Public visibility of Email Address and Spam 7 months ago

From Noam Preil to ~sircmpwn/public-inbox

My email is publicly visible on multiple sites
(including my own), and I've received one singular spam message to the
account _ever_, in the nearly two years I've used it.

It could just be that Migadu's spam filters are unusually good, but I
have it configured to filter to the spam folder, which. has exactly zero
spam entries in it right now.

That said, I've heard from others that they _did_ end up having to hide
their email on their own site to reduce spam, and that doing so
noticably reduced the rate at which they received it.

I'm just confused why I never get any, to be honest. I don't think I'm
doing anything _too_ unusual?

Re: [PATCH v5] implement line number info tracking 1 year, 13 days ago

From Noam Preil to ~mpu/qbe

Ping!

What's the status of this patch? Any changes needed?

Re: Relicensing aerc to GPL 1 year, 2 months ago

From Noam Preil to ~rjarry/aerc-devel

Hi,

I don't remember contributing to aerc, but if I did, I'm totally okay
with relicensing my contributions.

And, I got the email, so I assume I"m in the history for some reason? :P

...Okay, I just checked - my only contribution was changing the IRC link
from freenode to libera.chat. There's no way that's even a copyrightable
change, so my approval is unnecessary anyways.

Still, sending this in the interest of making your life easier - you can
remove my name from the list of people whose approval is needed!

[PATCH 2/2] strings::template: reject left braces 1 year, 6 months ago

From Noam Preil to ~sircmpwn/hare-dev

Signed-off-by: Noam Preil <noam@pixelhero.dev>
---
 strings/template/README      | 2 +-
 strings/template/template.ha | 4 +++-
 2 files changed, 4 insertions(+), 2 deletions(-)

diff --git a/strings/template/README b/strings/template/README
index 98a95f45..d693d45b 100644
--- a/strings/template/README
+++ b/strings/template/README
@@ -7,7 +7,7 @@ names must be alphanumeric ASCII characters (i.e. for which [[ascii::isalnum]]
returns true). A literal "$" may be printed by using it twice: "$$". Variables
may also be used with braces, i.e. ${variable}, so that they can be placed
immediately next to alphanumeric characters; such variables may include
[message trimmed]

[PATCH 1/2] strings::template: fix typo in README 1 year, 6 months ago

From Noam Preil to ~sircmpwn/hare-dev

Signed-off-by: Noam Preil <noam@pixelhero.dev>
---
 strings/template/README | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/strings/template/README b/strings/template/README
index 30d8d68f..98a95f45 100644
--- a/strings/template/README
+++ b/strings/template/README
@@ -7,7 +7,7 @@ names must be alphanumeric ASCII characters (i.e. for which [[ascii::isalnum]]
returns true). A literal "$" may be printed by using it twice: "$$". Variables
may also be used with braces, i.e. ${variable}, so that they can be placed
immediately next to alphanumeric characters; such variables may include
non-alphanumeric characters other than '_'.
[message trimmed]

re: Plan 9 "containers" 1 year, 6 months ago

From to ~sircmpwn/public-inbox

Hi,

> Even if you unmount them from your namespace - the "sandboxed" program 
> can mount them right back, by e.g. running the commands as listed in 
> ns's output.
> As far as I can tell, the only way to prevent that is the noattach flag 
> (set by RFNOMNT), which completely disables mount(). Obviously, that 
> breaks a lot of programs.

9front has features for more advanced sandboxing, including
auth/box, which allows specifying a full list of allowed drivers, and
constructing an arbitrary sandbox.

Moreover, quoth rfork(2):

Re: In praise of Plan 9: Plan 9 doesn't have true "mv"! 1 year, 6 months ago

From to ~sircmpwn/public-inbox

Quoth Ember Sawady <ecs@d2evs.net>:
> On Tue Nov 22, 2022 at 1:31 AM UTC,  wrote:
> > Renames are supported, but only within the same file system. They're not supported in _every_ case by mv(1) (currently, only within the same folder), but in principle it can be done. The main problem is that it's hard to know if two different folders are on the same file system.
> Seems to me that you could just try the fast rename and fall back to a
> copy if it fails, what's the reason that doesn't work?

Imagine you have this directory structure:

foo/
	bar/
	baz/
		a.c

and foo/ is bound over foo/bar, such that foo/bar/baz etc is equal to foo/baz, and the real, on-disk directory foo/bar *cannot* be accessed.

Re: In praise of Plan 9: Plan 9 doesn't have true "mv"! 1 year, 6 months ago

From to ~sircmpwn/public-inbox

Quoth Ember Sawady <ecs@d2evs.net>:
> On Tue Nov 22, 2022 at 1:31 AM UTC,  wrote:
> > Renames are supported, but only within the same file system. They're not supported in _every_ case by mv(1) (currently, only within the same folder), but in principle it can be done. The main problem is that it's hard to know if two different folders are on the same file system.
> Seems to me that you could just try the fast rename and fall back to a
> copy if it fails, what's the reason that doesn't work?

Imagine you have this directory structure:

foo/
	bar/
	baz/
		a.c

and foo/ is bound over foo/bar, such that foo/bar/baz etc is equal to foo/baz, and the real, on-disk directory foo/bar *cannot* be accessed.

Re: In praise of Plan 9: Plan 9 doesn't have true "mv"! 1 year, 6 months ago

From to ~sircmpwn/public-inbox

Quoth Askar Safin <safinaskar@gmail.com>:
> Hi. This letter is mostly not for Drew himself, but for everybody
> else. I hope that Drew's readers will read this mail and will know how
> bad Plan 9 actually is.

I use Plan 9 as my primary personal operating system, and am writing this within it.

> As you can see by carefully reading this source, "mv" always
> unconditionally COPIES file data (as opposed to Linux: Linux and all
> sane OS move files without copying when on the same file system)!

> As well as I remember I got this answer: this is because the 9P
> protocol (core file protocol in Plan 9) doesn't have move operation.