~torresjrjr

Europe/London

https://torresjrjr.com/

~torresjrjr/public-inbox

Last active 5 months ago

~torresjrjr/nest-devel

Last active 11 months ago

~torresjrjr/nest-announce

Last active 11 months ago

~torresjrjr/lateximgbot-devel

Last active 1 year, 3 months ago

~torresjrjr/lateximgbot-announce

Last active 1 year, 3 months ago

~torresjrjr/bezier.py-devel

Last active 1 year, 3 months ago

~torresjrjr/bezier.py-announce

Last active 1 year, 3 months ago

~torresjrjr/go-nestedtext-discuss

Last active 1 year, 7 months ago

~torresjrjr/go-nestedtext-devel

Last active 1 year, 7 months ago

~torresjrjr/go-nestedtext-announce

Last active 1 year, 7 months ago
View more

Recent activity

Re: [PATCH harelang.org] Change Russian greeting to Ukrainian a month ago

From Byron Torres to ~sircmpwn/hare-dev

I thought I'd let you know that this commit rubbed many of my Russian
friends the wrong way.

Some quotes, some translated:

> Switching Russian greeting to an Ukrainian one is pure politicizing. I
> would be totally okay if they just add a new one.

> Thought to try [Hare] in a commercial project. Well fuck now. [leaves
> chat]

> There is a political background here. I don't like it when politics
> interferes with free projects. We maintain neutral communication and
> respect for each other.

Re: RFC: Change of config format 2 months ago

From Byron Torres to ~rjarry/aerc-devel

On Sun Sep 11, 2022 at 7:53 PM BST, Moritz Poldrack wrote:
> On Sun Sep 11, 2022 at 8:06 PM CEST, Byron Torres wrote:
> > Also consider scfg.
> >
> > https://git.sr.ht/~emersion/go-scfg
>
> I think something that is more established would be better.

It has a ABNF grammer specification, unlikely to change, with 6 language
implementations. It's similar to OpenBSD's widely praised config syntax.

https://git.sr.ht/~emersion/scfg
https://why-openbsd.rocks/fact/configuration-syntax/

Re: RFC: Change of config format 2 months ago

From Byron Torres to ~rjarry/aerc-devel

Also consider scfg.

https://git.sr.ht/~emersion/go-scfg

Its simple and well defined.
Complex types aren't always suited for
configuration syntaxes. scfg's directives
should suffice for aerc.

---

Nonetheless, the current INI syntax seems to
work fine. Unless it has issues, why change?

Re: Switch style 3 months ago

From Byron Torres to ~sircmpwn/hare-users

Personally:

switch (o) {
case
        opcode::EQ, opcode::LT, opcode::GT, opcode::ADD,
        opcode::SUB, opcode::MUL, opcode::DIVMOD
=>
        calc(dat, o)?;
case =>
        void;
};


You could also do a double indent,

Re: [PATCH hare.vim 01/12] ftdetect: use setfiletype 3 months ago

From Byron Torres to ~sircmpwn/hare-dev

On Tue Aug 23, 2022 at 2:30 AM BST, Amelia Clarke wrote:
> On Mon Aug 22, 2022 at 6:18 PM MST, Byron Torres wrote:
> > I think you'll have a much higher chance of these patches being merged
> > if you commit to using them for a week, make sure they work, edit
> > accordingly, and send a singular, complete v2 patchset.
>
> I have been using things as they currently are for long enough that I am
> sure they work correctly,

Fair enough

> I just previously forgot to account for the fact that changes to the
> earlier patches would invalidate the diffs of the later one.

Re: [PATCH hare.vim 01/12] ftdetect: use setfiletype 3 months ago

From Byron Torres to ~sircmpwn/hare-dev

On Tue Aug 16, 2022 at 3:39 AM BST, Amelia Clarke wrote:
> Signed-off-by: Amelia Clarke <me@rsaihe.dev>

This confusing tree of patches has gotten out of hand. You've got
multiple revision patches replying to the wrong parents patches.

I think you'll have a much higher chance of these patches being merged
if you commit to using them for a week, make sure they work, edit
accordingly, and send a singular, complete v2 patchset.

Re: Aerc icon contest 3 months ago

From Byron Torres to ~sircmpwn/aerc

On Thu Aug 11, 2022 at 6:49 PM BST, Moritz Poldrack wrote:
> On Thu Aug 11, 2022 at 7:48 PM CEST, Byron Torres wrote:
> > How about something like this?
> Reminds me a bit of my entry :D

A bit, yeah. It seemed a little to generic, like perhaps could have been
a styled Arch Linux thing or something. I added the curve at the top,
and the little flick curve at the bottom, just to kinda go with the
curvyness of the letters of "aerc".

> but I think we need at least an SVG to go with ^^

Fair enough. Maybe I'll try some other time. I had in mind some kind of
curvy fountain pen style "A" with that flick. Again, something unique.

Re: Aerc icon contest 3 months ago

From Byron Torres to ~rjarry/aerc-discuss

On Thu Aug 11, 2022 at 6:49 PM BST, Moritz Poldrack wrote:
> On Thu Aug 11, 2022 at 7:48 PM CEST, Byron Torres wrote:
> > How about something like this?
> Reminds me a bit of my entry :D

A bit, yeah. It seemed a little to generic, like perhaps could have been
a styled Arch Linux thing or something. I added the curve at the top,
and the little flick curve at the bottom, just to kinda go with the
curvyness of the letters of "aerc".

> but I think we need at least an SVG to go with ^^

Fair enough. Maybe I'll try some other time. I had in mind some kind of
curvy fountain pen style "A" with that flick. Again, something unique.

Re: Aerc icon contest 3 months ago

From Byron Torres to ~rjarry/aerc-devel

On Thu Aug 11, 2022 at 6:49 PM BST, Moritz Poldrack wrote:
> On Thu Aug 11, 2022 at 7:48 PM CEST, Byron Torres wrote:
> > How about something like this?
> Reminds me a bit of my entry :D

A bit, yeah. It seemed a little to generic, like perhaps could have been
a styled Arch Linux thing or something. I added the curve at the top,
and the little flick curve at the bottom, just to kinda go with the
curvyness of the letters of "aerc".

> but I think we need at least an SVG to go with ^^

Fair enough. Maybe I'll try some other time. I had in mind some kind of
curvy fountain pen style "A" with that flick. Again, something unique.

Re: Aerc icon contest 3 months ago

From Byron Torres to ~rjarry/aerc-discuss

How about something like this?

	.......@............
	.....@@@@@..........
	....@@...@@.........
	...@@.....@@........
	..@@@@@@@@@@@@@@@...
	.@@.........@@......
	.@...........@......
	@.............@.....
	...............@...@
	................@@@.
	....................