From: Iain Parris <ipv2.lst@parris.org>
To: Willem <willvdw@gmail.com>
Cc: supmua <supmua@googlegroups.com>
Subject: Re: [sup] Re: sup is up
Date: Tue, 23 Jun 2020 20:31:04 +0100 [thread overview]
Message-ID: <1592934707-sup-1570@ceres> (raw)
In-Reply-To: <ff5bdbde-c568-ed0e-f498-808e274da75f@gmail.com>
Hi Willem,
Excerpts from Willem's message of 2020-06-23 11:12:50 +0200:
> In our recent communication I expressed my great appreciation when I
> heard that my favorite email client has been rescued from a sad
> extinction. I have been using sup off and on for more than 8 years and
> in the mean time I have tried many others like mutt, mu4e, notmuch etc,
> but I keep coming back to sup as it simply works best for the way I like
> doing email.
>
> I am sending this follow up to the mailing list in the hope that there
> is additional interest in discussion about sup and the various linux
> distributions.
Thank you very much again for emailing, and for kicking off the
discussion about distributions / platforms. It's great to hear from
another happy sup user. I am exactly the same - I keep coming back to
sup. :-)
> But, because of the problem that sup works only on ruby 2.3.3 and Arch
> uses a newer version of ruby, one has to use a workaround that is
> thankfully fully described on the Sup-ArchWiki which then directs you to
> the RVM-ArchWiki with good instructions for installing RVM and then sup.
>
> This RVM workaround is referred to in the Sup-ArchWiki as a temporary
> install, and I discovered why; one of the draw backs is that after some
> linux kernel updates sup stops working and an alias needs to be added to
> ~/.bashrc again.
The ArchWiki documentation is very good, and has often helped me in the
past because it is regularly widely applicable and clear documentation,
even for users like me of other Linux distributions.
The key patch required for sup to run on later Ruby versions is
<https://github.com/sup-heliotrope/sup/commit/55f6b77ab6327495241e3c2ced6e33cb6ee8dd35>
- credit to Dan.
This patch will be included in the upcoming next sup release, but in the
meantime I've checked on Arch Linux in a VM, and found a method to apply
the patch and run sup successfully using system Ruby.
Pending the next sup release, I've updated ArchWiki right now with the
new workaround instructions for Arch Linux - and hope that it helps you,
and possibly others too!
<https://wiki.archlinux.org/index.php/Sup#Option_1_(recommended):_RubyGems_with_current_system_Ruby>
Please do let me know if that works for you.
> This is why when you mentioned in your item (4) "Collaborate with major
> downstream packagers"; I thought it would be great if you included Arch
> Linux in this group as I believe sup fits in perfectly with the Arch
> Linux philosophy, one item of which is minimal bloat. I am currently
> using sup on Arch Linux with the i3 tiling window manager which I really
> enjoy; cutting edge and bloat free, although I still have to find the
> time to sort out some sup hooks.
Sounds good - I'll add Arch Linux to my mental list of distributions.
I also have a note on my to-do list to update the sup wiki
<https://github.com/sup-heliotrope/sup/wiki> with recent installation
instructions for various platforms.
Does anyone else reading have any requests for other distribution or
platform? So far on my mental list is Debian, Ubuntu, Fedora, Arch,
?MacPorts.
Kind regards,
Iain
next prev parent reply other threads:[~2020-06-23 19:31 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-23 9:12 Willem
2020-06-23 19:31 ` Iain Parris [this message]
2020-06-24 11:29 ` Willem
-- strict thread matches above, loose matches on Subject: below --
2020-06-14 22:08 Iain Parris
2020-06-16 7:31 ` Dan Callaghan
2020-06-21 8:51 ` [sup] " Matthieu Rakotojaona
2020-06-21 12:48 ` Iain Parris
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1592934707-sup-1570@ceres \
--to=ipv2.lst@parris.org \
--cc=supmua@googlegroups.com \
--cc=willvdw@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox