Re: New Package for NonGNU-ELPA: clojure-ts-mode

[Eli Zaretskii]

> From: Ihor Radchenko <yantar92@posteo.net>
> Cc: dmitry@gutov.dev, jschmidt4gnu@vodafonemail.de, philipk@posteo.net,
>  luangruo@yahoo.com, stefankangas@gmail.com, emacs-devel@gnu.org
> Date: Fri, 01 Sep 2023 13:31:05 +0000
> 
> Eli Zaretskii <eliz@gnu.org> writes:
> 
> >> I can turn them off selectively in my MUA.
> >> IMHO, this is not any different from how I approach mailing lists - most
> >> of the discussions on ML are not interesting to me and I simply filter
> >> them out. I think Gnus scoring is relevant (although I use different
> >> approach).
> >
> > How is this consistent with complaints about the difficulties of using
> > a MUA in sophisticated ways?
> 
> This branch started from your claim that in order to use GitHub one
> needs to check each repo manually:
> 
>   > What I'm trying to say here is: Email might look like it's easy to use,
>   > but in the context of a mailing list it's not necessarily so, even from
>   > the technical side.  These text entry boxes on Github et al. definitely
>   > feel easier and more inviting to use.
>  Yes, but the cost is that you need to proactively to visit each and
>  every GitHub repository to see whether something new was posted in the
> 
> But it is not, and email workflow (if one wants to use that kind of
> workflow) is still viable.

Are you actually using that with GitHub repositories?  Because I do,
and my comments about that are based on several years of doing it.
It's extremely tedious, to say the least, and following a discussion
is without visiting the corresponding issue in a Web browser is quite
hard, IME.  So please believe me when I say this is very annoying.

> > Really?  Just look at this discussion: each message clearly shows to
> > what it responds by quoting that text.
> 
> Check out https://github.com/radian-software/straight.el/issues/1107,
> for example. Do you find it confusing?

That's a Web page, not an email inbox.  And yes, I'd find it hard to
read due to very few quotes.  And that discussion is unusual in how
much people quote one another.  But still, take a random message
there:

  
https://github.com/radian-software/straight.el/issues/1107#issuecomment-1670440497

It says "Should be fixed by #1109" without saying what is fixed.

Or this post:

  
https://github.com/radian-software/straight.el/issues/1107#issuecomment-1668343604

It begins with "The function in question is" and goes on to discussing
code, without saying to which part of the discussion this refers.
Imagine that you receive an email like that -- how do you know what is
this about without re-reading the entire discussion?

Of course, people can refrain from quoting in email messages as well.
But my point is that when people use the Web UI, they can easily
forget that someone might be reading their responses via email,
without seeing the previous posts.