From: Willem <willvdw@gmail.com>
To: supmua@googlegroups.com
Cc: Iain Parris <ipv2.lst@parris.org>, Dan Callaghan <djc@djc.id.au>
Subject: [sup] Re: sup is up
Date: Tue, 23 Jun 2020 11:12:50 +0200 [thread overview]
Message-ID: <ff5bdbde-c568-ed0e-f498-808e274da75f@gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1969 bytes --]
Hi Iain (and all sup fans)
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.
When I first started using sup it was not available via Arch Linux, so I
found it easier (mostly because of my own lack of programming
knowledge...) to install into Lubuntu and later Debian. More recently I
have been using Arch Linux so I checked the ArchWiki and was pleased to
see sup there!
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.
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.
I believe many other dedicated sup users would find this sort of set up
very satisfying!!
So, thanks again Iain
Cheers
Willem
[-- Attachment #2: Type: text/html, Size: 2435 bytes --]
next reply other threads:[~2020-06-23 9:12 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-23 9:12 Willem [this message]
2020-06-23 19:31 ` Iain Parris
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=ff5bdbde-c568-ed0e-f498-808e274da75f@gmail.com \
--to=willvdw@gmail.com \
--cc=djc@djc.id.au \
--cc=ipv2.lst@parris.org \
--cc=supmua@googlegroups.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