~brown121407

Râmnicu Sărat, România

https://brown.121407.xyz

Passionate about GNU/Linux and Free Software.

~brown121407/blog-discussion

Last active a month ago

~brown121407/ml

Last active a month ago
View more

Recent activity

Re: [PATCH] Dumb support for pinning. 7 days ago

From Alexandru-Sergiu Marton to ~brettgilio/org-webring

Brett Gilio <brettg@gnu.org> writes:

> ...
> 
> 2. Somewhere along the line, <nil/> is getting inserted into the
> non-pinned articles which is messing up the styling of those items. You
> can check https://brettgilio.com/ for an example of this.
>
> ...
>
> If you, or anybody gets a moment an wants to take a crack at 1 or 2,
> please go for it!

[PATCH] Dumb support for pinning. 8 days ago

From Alexandru-Sergiu Marton to ~brettgilio/org-webring

---

This is a quick and dirty way of pinning items. It works only for the
webring, as it's mostly a kind of proof of concept. I didn't have the
time to make something cleaner right now, but I will probably come
back to this soon.

To pin an article you have to add its URL to the
org-webring-pinned-urls list.

The final webring will contain all the pinned items first (of course,
limited by org-webring-items-per-source and org-webring-items-total),
sorted chronologically, followed by as many normal articles the
settings allow. The pinned items in HTML form also have the "pinned"
[message trimmed]

Re: `encode-time' failing on 27.1 a month ago

From Alexandru-Sergiu Marton to ~brettgilio/org-webring

Hi,

I've been able to reproduce this on GNU Guix System with Emacs 27.1. It
seems that parse-time-string doesn't yet understand the Atom
timestamps. We could do employ a workaround until we figure it out: if
iso8601-parse is bound, use it to parse the timestamps, otherwise use
parse-time-string on our string hack.

--8<---------------cut here---------------start------------->8---
(parse-time-string "2020-06-24T17:00:00+0200")
=> (nil nil nil nil nil nil nil -1 nil)

(iso8601-parse "2020-06-24T17:00:00+0200")
=> (0 0 17 24 6 2020 nil nil 7200)

Re: Thoughts on syndicates list a month ago

From Alexandru-Sergiu Marton to ~brettgilio/org-webring

Brett Gilio <brettg@gnu.org> writes:

> Alexandru-Sergiu Marton <brown121407@posteo.ro> writes:
>
>> org-webring-generate-webring could maybe accept an optional parameter
>> for creating the syndlist to plug it in just before the version and
>> attribution.
>
> I think probably having it as an extra parameter of the
> `org-webring-generate-webring' function is the easiest of the options,
> and in that case would be easiest to keep in the org-webring.el file and
> not parse it out into its own file.

We could do the parsing in an external file to be clean, if need be, and

Re: Thoughts on syndicates list a month ago

From Alexandru-Sergiu Marton to ~brettgilio/org-webring

Brett Gilio <brettg@gnu.org> writes:

> The issue that stands is mostly, how the hell should we have this
> displayed? Should it be on its own page? If so, how should it be
> formatted? Or should it be optional to put it on its own page, and
> perhaps place it beneath the result of `org-webring-generate'. Lots of
> possibilities here, and extensibility of the whole thing is no barrier
> either.

Disclaimer: I'm on the verge of falling asleep, so I can't guarantee the
integrity of those thoughts.

I think allowing the user to somehow choose between embedding it after
the webring or having it _more standalone_ is a good idea, though I'm

WIP: Guix package. a month ago

From Alexandru-Sergiu Marton to ~brettgilio/org-webring

Hi,

I was thinking about how we should proceed regarding writing a Guix
package definition. Should we include a guix.scm file in the project,
should we send a patch directly to Guix? Maybe both? Let me know what
you think.

Anyways, here's what I have so far:

--8<---------------cut here---------------start------------->8---
(use-modules (gnu packages emacs)
	     (gnu packages emacs-xyz)
	     (guix)
	     (guix build-system emacs)

Re: [PATCH] Add support for atom feeds a month ago

From Alexandru-Sergiu Marton to ~brettgilio/org-webring

Jamie Beardslee <jdb@jamzattack.xyz> writes:

> I don't actually have access to 26, so please let me know whether this
> works.
>
> This patch should be applied on top of the previous one.

It does work! Thanks. We'll integrate this very soon.

One more thing regarding timestamps. Our hack works nice for now, but I
found something interesting.

parse-time-string turns out to be more flexible than I thought. We can
even add timezone info at the end of our hacky format if we manage to

Re: [PATCH] Add support for atom feeds a month ago

From Alexandru-Sergiu Marton to ~brettgilio/org-webring

Jamie Beardslee <jdb@jamzattack.xyz> writes:

> Is it too early to consider 27 the baseline?  Maybe we should fallback
> to a minimal parser if (fboundp 'iso8601-parse) returns nil, or perhaps
> the trusty 1 Jan 1970?
>
> Let me know what you think.

The minimal parse you're talking about sounds like a good idea.

While Emacs 26.3 doesn't know how to parse this whole thing:
"2020-01-22T00:00:00+00:00", it can partially understand this:
"2020-01-22".

Re: Added "Syndicates List" entry to TODO. a month ago

From Alexandru-Sergiu Marton to ~brettgilio/org-webring

Brett Gilio <brettg@gnu.org> writes:

> If anybody has any ideas for how to do this, I encourage patches or
> development on a new branch, as well as responses to this email for
> collaboration.

Hi,

The easiest place to plug such a thing seems to be in
org-webring--get-items-from-url, altough the name of the function
doesn't exactly match this extra functionality. Adding this to the
let-form in that function should generate a very primitive
syndicates.org file.

Re: [PATCH] Add support for atom feeds a month ago

From Alexandru-Sergiu Marton to ~brettgilio/org-webring

Hi,

Thanks for the patch. Overall, it /looks/ pretty well, but I ran into
a problem with it. It doesn't know how to handle Atom dates.

We currently use =parse-time-string= to parse RSS dates, which follow
RFC 822 (http://www.faqs.org/rfcs/rfc822.html). Atom, on the other hand,
uses the timestamp specification from RFC 3339
(http://www.faqs.org/rfcs/rfc3339.html), which Emacs doesn't know how to
handle and just returns a list of nils (at least on my end).

> Tested with dozens of atom and rss feeds I found from all over the
> place, with no noticeable errors on org-webring's end.