nyc
software engineer
From alex wennerberg to ~aw/fishbb-devel
Hi! thanks for the rec, I did explore this, but I ended up deciding on something more radically simple, which is the gemini text format alex alexw.nyc > On Aug 25, 2024, at 12:13 PM, Leo Heitmann Ruiz <leo@heitmannruiz.org> wrote: > > Hey :) > > Regarding your post at <https://merveilles.town/@aw/112875711699347167>: > > You might be looking for <https://djot.net/>. > > Warmly,
From Alex to ~aw/flounder
Hi Michael! i agree, this is an issue I’ve been meaning to resolve for a while, I just haven’t spent a lot of time on the flounder code base lately. I’ll get around to it eventually. Thanks for the suggestion! Alex > On Dec 1, 2023, at 3:10 PM, Michael Mientus <michael.mientus@gmail.com> wrote: > > I have another request. On the HTML proxy, /updates/[capsule] gives a > list of recently modified files. For example: > > => https://flounder.online/updates/pwshnotes flounder > >> Recently updated files from pwshnotes.flounder.online >> 13 days ago index.gmi >> 13 days ago gemlog/2023-11-18-nation-books.gmi
From alex wennerberg to ~aw/flounder
Yep, this was a bug introduced recently when I tried to fix a different bug... I'll see if I can fix it, but it may be a while before I get around to it. Thanks for reporting! Alex On Sat Nov 18, 2023 at 2:09 PM EST, Michael Mientus wrote: > The gemlog directory has an automatically generated page title in the > form of [so-and-so]'s Gemlog > > On the HTTP proxy, my title shows as: > Pwshnotes's Gemlog > > It seems the title is double escaped using:
From Alex to ~aw/flounder
it may be an issue because the file name has a space in it! I can investigate later but try renaming the file first Alex > On Oct 23, 2023, at 5:04 PM, 84001 <84001@riseup.net> wrote: > > hello > > my "bug" and question is : > how can i delete gemlogs ? > i tried severas times with the delete ( red in color ) option > with no result > any trick missing ? > thanks for any guidance !
From alex wennerberg to ~vdupras/duskos-discuss
On Sat Jun 17, 2023 at 8:38 AM EDT, Virgil Dupras wrote: > The most straightforward way to go about this isn't to mangle with dictionaries, > but to overwrite the "abort" alias with "realias". > > I also don't understand why you're trying to overload "abort"" rather than > "abort". Both of these choices came from me having an incomplete understanding of a lot of the foundational words in Dusk. I read a bunch of the documentation/code today and I think I have a better understanding of the dictionary structure / compiling words. I'll look into sending an updated patch soon! > Do you think you have all details you need to carry on? Don't hesitate to ask
From alex wennerberg to ~vdupras/duskos-discuss
Found this a bit unclear, since my understanding is isn't exactly the same as entry (it does not take a dict param but refers to sysdict) --- Still learning git-send-email and best practices. I believe that this should be a comment that doesn't affect the patch. My first version of this commit had a couple typos, my apologies. fs/doc/dict.txt | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/fs/doc/dict.txt b/fs/doc/dict.txt index 3cb3d79..f19da1c 100644 --- a/fs/doc/dict.txt +++ b/fs/doc/dict.txt [message trimmed]
From alex wennerberg to ~vdupras/duskos-discuss
--- fs/doc/usage.txt | 7 ++++--- 1 file changed, 4 insertions(+), 3 deletions(-) diff --git a/fs/doc/usage.txt b/fs/doc/usage.txt index b2ea897..9ab418a 100644 --- a/fs/doc/usage.txt +++ b/fs/doc/usage.txt @@ -46,9 +46,10 @@ Dusk has no DEC/HEX mode. Number literals are parsed using a prefix system. ## Strings A string is an address to an area in memory starting with a length byte followed by that many bytes. When we refer to a "string", we refer to that address. For[message trimmed]
From alex wennerberg to ~vdupras/duskos-discuss
--- fs/doc/usage.txt | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/fs/doc/usage.txt b/fs/doc/usage.txt index aafd043..b2ea897 100644 --- a/fs/doc/usage.txt +++ b/fs/doc/usage.txt @@ -68,7 +68,7 @@ character: \n: newline ($0a) \r: carriage return ($0d) \0: 0 \0: null byte (0)[message trimmed]
From alex wennerberg to ~vdupras/duskos-discuss
Found this a bit unclear, since my understanding is isn't exactly the same as entry (it does not take a dict param but refers to sysdict --- fs/doc/dict.txt | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/fs/doc/dict.txt b/fs/doc/dict.txt index 3cb3d79..5891ae0 100644 --- a/fs/doc/dict.txt +++ b/fs/doc/dict.txt @@ -276,7 +276,7 @@ w>e w -- e Yield an entry (linked list pointer) from a word reference. e>w e -- w Yield a word reference (executable) from an entry. entry 'dict s -- Create entry with name s in dictionary 'dict. [message trimmed]
From alex wennerberg to ~vdupras/duskos-discuss
On Thu Jun 15, 2023 at 7:12 AM EDT, Virgil Dupras wrote: > Hello Alex, > > Yes, that's a problem, good catch. Ideally, we'd add a kind of "abort hooks" > system, a chain of words to hook together, a bit like the idle loop (except I > think in this case we could simply use "chain"), which we call on abort. > lib/alloc would hook "unlockhere" in there. Ok, so I have skeched out; : unlockabort" ' unlockhere ' abort" chain execute ; What I'm wondering is, how could I make this more generic? I don't know enough about the dict internals (in dusk or in forth in general), but