On 4/5/21 3:41 PM, Drew DeVault wrote:
> This is intended, yes. 

Thanks for the clarification.

> You should commit a proper fix upstream if you want to associate it
> with, well, the upstream project.

Well, the issue with the build[1] wasn't caused by an upstream change, 
though. That's why I resubmitted the build instead of committing 
something upstream.

1: see task "setup" line 3

For example, the following build failed because of what seems to be a 
sr.ht error:

	https://builds.sr.ht/~admicos/job/477851

I resubmitted the build from the button next to it, and it created this 
new job:

	https://builds.sr.ht/~admicos/job/477853

However, the second build is not listed under the same "project" as the 
first, which makes it hard to find:

	https://builds.sr.ht/~admicos/moonlander

On 3/29/21 9:22 AM, almaember wrote:
> One question, what do you do if a single line is split into multiple
> chunks?

https://git.ebc.li/_/moonlander/src/branch/main/gemtext/src/lib.rs

The chunked_parse (Line 160) function reads character by character, 
saving everything into an "incomplete line" buffer (Line 31), and when 
it encounters a newline it empties and processes the incomplete line 
buffer and returns the list of "line objects" corresponding to the 
markup inside the buffer.

When the connection is closed, the finalize function (Line 221) runs and 
parses the incomplete line buffer one last time to complete the document.

On 3/28/21 11:07 PM, almaember wrote:

> or how much time it's going to take to download, or if it's even going > to end at all.

As far as I'm aware no client has solved this. If TLS close_notify gets 
standardized we might get a "connection failed" state, but other than 
that you won't be able to know how long the content is and whether you 
successfully downloaded it or not.

> My ideas as of right now:
> 
>   - Have a big buffer and store everything in it until the connection is
>     closed. The connection would be terminated if:
>      - the connection closes

Thanks for trying it out. I had plans to eventually try Moonlander with
a screen reader, but you seem to have beaten me to it :p

> * The text of the page cannot be read by arrow keys. the keys move
> throughout the text, but Orca doesn't read it.

So it doesn't read it at all? Not even as a big blob of text without any
formatting? I would've expected it to be un-formatted but still readable
considering it's still native widgets powering everything.

Though this isn't that big of a deal as I would've needed to create a
different "accessibility view" manually _anyway_, as the visual
formatting is done in a pretty hacky way that doesn't provide any
"structure" a screen reader or whatnot can detect.

Hello, citizens of the Gemini mailing list!

Back in May 19, I announced Moonlander here:
    https://lists.orbitalfox.eu/archives/gemini/2020/000870.html

Unfortunately, that didn't last long. As quickly as it came, it went
away into the land of "broken, unmaintained pile of FOSS".

Today, I bring you, Moonlander! Well, a rewrite using the same name, but
hey, the only thing that matters is how fancy it looks, right?

Moonlander (then: "The fanciest Gemini client in the entire solar
system.", now: "Just another 'fancy' Gemini client") is a graphical
Gemini client, developed using Rust and GTK 3, to use under Linux.

The archive URLs are going to change in a week or so, as I'm working on
changing parts of the server hosting them, so this patch doesn't exactly
make sense to apply, at least for now.

I'd recommend you move what you want from my repo into somewhere else
you control. I haven't touched this repo (and Computercraft as a whole)
for a long time now, and I don't really see the point in keeping these
working.

--
Have a nice /(day|night|week(end)?)/
~ Ecmel B. Canlıer ~

I probably have the hackiest setup here, based on shell scripts, duct
tape, and some JS on the deployment parts.

https://git.ebc.li/admicos/blog

I create a new `.gmi` file under `pages/<category>` and add some
boilerplate header and footer lines (for my shell-based templating
thing)

Then I edit the `post_list` file to add the new page. If I put the `.gmi`
extension on the filename here, the page becomes Gemini-exclusive.

Finally, I push my changes into the repo above, which pings a HTTP
endpoint I am listening to via https://nodered.org, clones the repo and

> I also set up a mailing list on Sourcehut (like, just now) to leave
> comments.  I've linked the mailing list at the bottom of my weblog
> entries,

Thinking about it, I should do that too.

> One last question: Gemininauts (please oh please let that be a word)
> with twinlogs, how do you decide what to cross-post and what to keep
> {WWW,gemini,gopher}-exclusive? I'm leaning towards keeping my weblog
> more "professional" and my gemlog less filtered, [...] I'm curious
> to know how you all handle this.

I separate my posts into three (for now, at least) categories, being
"experiments", "posts" and "micro logs".

On Thu Nov 12, 2020 at 12:18 PM +03, Jason McBrayer wrote:
> Which markers should we use? [...] We can use '_', but it's less used
> (to imply underlines). I'm open to suggestions.

Using '_' would also conflict with snake_cased_variables in various
programming contexts, which would also require the addition of a "inline
preformatted" marker, which probably would complicate this even more.

--
Have a nice /(day|night|week(end)?)/
~ Ecmel B. Canl?er ~