From: John Soo <jsoo1@asu.edu>
To: Tanguy Le Carrour <tanguy@bioneland.org>
Cc: guix-devel@gnu.org
Subject: Re: Introducing myself
Date: Thu, 18 Apr 2019 16:52:01 -0700 [thread overview]
Message-ID: <78700CC6-FB70-4B7C-99B0-92C7721F8DEE@asu.edu> (raw)
In-Reply-To: <20190418201934.d5jhcc5voqar7hvc@melmoth>
Hi Tanguy,
I just realized you said you wanted an fzf replacement. I recommend fzy. It’s not quite as full featured as fzf but it gets the job done.
- John
> On Apr 18, 2019, at 1:19 PM, Tanguy Le Carrour <tanguy@bioneland.org> wrote:
>
> (I've just realised that there was a typo in the subject… shame on me!
> … fixed… unfortunately the Internet never forgets!!)
>
>
> Le 04/17, Pierre Neidhardt a écrit :
>> Tanguy Le Carrour <tanguy@bioneland.org> writes:
>>> I'll try to package my favourite tools that
>>> are currently missing: ack, fd, fzf, udiskie, poetry, pyenv…
>>
>> Suggested alternatives:
>>
>> - ack -> the-silver-searcher (ag)
>
> Thanks! I came across this one some time ago. This might be the
> perfect time to evaluate/adopt it!
>
>
>> - fzf -> Emacs with Ivy or Helm
>
> arg… this is the much feared moment when I have to confess that I'm…
> a faithful Vim user! ^_^'
>
>
>> - udiskie -> See discussion here:
>> https://lists.gnu.org/archive/html/help-guix/2018-03/msg00331.html.
>> At some point, we could supersede both udiskie or home-baked scripts
>> with Guix/Shepherd user services.
>
> I'm really happy with my Bspwm [1] setup, even if it comes with absolutely no
> removable media management! I used to use `udiskctl`, but I have to
> admit that one quickly gets attached to `udiskie`.
>
> [1]: https://github.com/baskerville/bspwm
>
>
> I guess the real struggle will be replacing dependency management
> in my Python projects. But that's a totally different topic!
>
> Regards
>
> --
> Tanguy
>
next prev parent reply other threads:[~2019-04-18 23:53 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-13 8:57 Introducting myself Tanguy Le Carrour
2019-04-13 10:42 ` Pierre Neidhardt
2019-04-15 20:32 ` Tanguy Le Carrour
2019-04-17 5:31 ` Chris Marusich
2019-04-17 19:50 ` Tanguy Le Carrour
2019-04-17 21:23 ` Pierre Neidhardt
2019-04-18 20:19 ` Introducing myself Tanguy Le Carrour
2019-04-18 23:52 ` John Soo [this message]
2019-04-19 21:21 ` Tanguy Le Carrour
-- strict thread matches above, loose matches on Subject: below --
2019-05-10 21:25 Jakob L. Kreuze
2019-05-10 23:03 ` Laura Lazzati
2019-05-10 23:54 ` Tobias Geerinckx-Rice
2019-05-11 2:05 ` Timothy Sample
2019-05-11 12:27 ` Ludovic Courtès
2019-05-11 19:22 ` Gábor Boskovits
2019-05-13 18:55 ` Christopher Lemmer Webber
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=78700CC6-FB70-4B7C-99B0-92C7721F8DEE@asu.edu \
--to=jsoo1@asu.edu \
--cc=guix-devel@gnu.org \
--cc=tanguy@bioneland.org \
/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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).