~jasval

~jasval/testing-list

Last active 10 months ago
View more

Recent activity

Re: Why hard wrap at 72 in lists 8 months ago

From Jason Valencia to ~sircmpwn/sr.ht-discuss

Ludovic Chabant wrote:
> > Alright, I can understand that logic. Still, hard-wrapping is as
> > anachronistic as a physical printing press.
>
> I also don't like this aspect of lists.sr.ht. The RFC 2646's comment
> about line wrapping was, first, only a suggestion, and, second,
> written long before devices with widely different display sizes were
> invented. As a result, looking at lists.sr.ht on a smartphone is a
> poor experience, since we have to scroll horizontally all the time to
> read messages. Same thing when reading it using a smaller (<70ch) TWM
> pane or something. If anything, I'd love to see this fixed, since,
> regardless of anybody's opinions on the general matter of mailing list
> etiquette, this is clearly a web UX bug.

Named lets in Fennel 8 months ago

From Jason Valencia to ~technomancy/fennel

Scheme has a concept of "named lets", essentially a let you can call
from within itself, which is useful for recursion.

R5RS [1]:
> (let <variable> <bindings> <body>)
>
> "Named let" is a variant on the syntax of let which provides a more
> general looping construct than do and may also be used to express
> recursions. It has the same syntax and semantics as ordinary let
> except that <variable> is bound within <body> to a procedure whose
> formal arguments are the bound variables and whose body is <body>.
> Thus the execution of <body> may be repeated by invoking the procedure
> named by <variable>.

Re: [PATCH] Drop minimum meson version to 0.37.1 10 months ago

From Jason Valencia to ~emersion/mrsh-dev

Jason Valencia wrote:
> Simon Ser wrote:
> > (As a side note, git-am refused to apply your patch, failing with
> > "error: corrupt patch at line 17". I don't know why this happened,
> > can you make sure you're using git-send-email [1]?)
>
> It looks like I made some other commits/changes before my patch; the
> hashes in my patch don't match any in the repo. If you correct the
> hashes in the index line it applies cleanly.
>
> Sorry about that! I'll be more careful.

I messed up the formatting.

Re: [PATCH] Drop minimum meson version to 0.37.1 10 months ago

From Jason Valencia to ~emersion/mrsh-dev

Simon Ser wrote:
> (As a side note, git-am refused to apply your patch, failing with
> "error: corrupt patch at line 17". I don't know why this happened, can
> you make sure you're using git-send-email [1]?)

It looks like I made some other commits/changes before my patch; the
hashes in my patch don't match any in the repo. If you correct the
hashes in the index line it applies cleanly.

Sorry about that! I'll be more careful.

[PATCH] Drop minimum meson version to 0.37.1 10 months ago

From Jason Valencia to ~emersion/mrsh-dev

The minimum required meson version is 0.43.0, but no features are
actually being used that are incompatible with 0.37.1 (the latest
version shipped by Debian).
---
 meson.build | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/meson.build b/meson.build
index 6d607a0..f4e719e 100644
--- a/meson.build
+++ b/meson.build
@@ -3,7 +3,7 @@ project(
 	'c',
 	version: '0.0.0',
[message trimmed]

Re: [PATCH lists.sr.ht] Wrap long lines for better readability 10 months ago

From Jason Valencia to ~sircmpwn/sr.ht-dev

Drew DeVault wrote: 
>> --inline works with git send-email too. I should've used it as an 
>> example as it is more relevant. (E.g. git send-email --inline -1.) 
>
> Sorry, my meaning is that I don't want to require extra flags at all 
> for send-email/format-patch. 

Oh. You can run a command to set multipart as the default either 
per-project or globally. You already probably set the default To: 
address with git config, and many projects already have certain 
settings they ask you use (like signing off, or subject prefixes).

Re: [PATCH lists.sr.ht] Wrap long lines for better readability 10 months ago

From Jason Valencia to ~sircmpwn/sr.ht-dev

Drew DeVault wrote: 
> On 2018-11-17  7:16 PM, Jason Valencia wrote: 
>> I think a decent way to handle this would be parsing email marked as 
>> format=flowed and outputting actual basic HTML. f=f has a set way to 
>> unambiguously show what is quoted text vs. what is a literal > sign, 
>> so quotes could be rendered with <blockquote> tags (this will make 
>> nested quotes nice to read). 
>
> I'm a bit hesitant to do this on screens wide enough to display the 
> original email faithfully, but open to it on e.g. mobile. 

The point of format=flowed is to allow you to wrap lines and display 
quotes how you want, so it isn't exactly unfaithful. A sender using f=f 
is expressing that the exact presentation of the content does not

Re: [PATCH lists.sr.ht] Wrap long lines for better readability 10 months ago

From Jason Valencia to ~sircmpwn/sr.ht-dev

Here are some of my thoughts: 

I think a decent way to handle this would be parsing email marked as 
format=flowed and outputting actual basic HTML. f=f has a set way to 
unambiguously show what is quoted text vs. what is a literal > sign, so 
quotes could be rendered with <blockquote> tags (this will make nested 
quotes nice to read). 

(The HTML would only need <p>, <br />, and <blockquote> tags.) 

Code and patches could be sent as inline attachments; this way we can 
have regular text wrap nicely, and code be displayed as-is (this also 
means users could, if they wanted, display text in a proportional font 
while displaying code monospaced). (You can use git format-patch

Regular attachment test 10 months ago

From Jason Valencia to ~jasval/testing-list

Test email with a regular attachment.

Inline attachment test 10 months ago

From Jason Valencia to ~jasval/testing-list

This is a test email with an inline attachment.