unofficial mirror of guile-user@gnu.org 
 help / color / mirror / Atom feed
From: zimoun <zimon.toutoune@gmail.com>
To: Ricardo Wurmus <rekado@elephly.net>
Cc: Julien Lepiller <julien@lepiller.eu>, guile-user@gnu.org
Subject: Re: scheme with vim
Date: Wed, 29 Jan 2020 21:29:37 +0100	[thread overview]
Message-ID: <CAJ3okZ0CKggE6UEen5m2ZKtPOhincZMd5pmoUWH+0jUyCeR0gQ@mail.gmail.com> (raw)
In-Reply-To: <87pnf2t8l9.fsf@elephly.net>

Hi Ricardo,

On Wed, 29 Jan 2020 at 19:36, Ricardo Wurmus <rekado@elephly.net> wrote:

> > i don't know what is the good way to get the list of built-in
> > commands of guile so i ended up with
> >
> >     aptitude search '~i ~n guile-2' -F%p |
> >         xargs -n1 dpkg -L |
> >         perl -lnE 'print if /[.]scm$/ && -f' |
> >     ctags -L - -f ~/.vim/ctags/guile
> >
> > any better way ?
>
> I don’t have aptitude or dpkg on my Guix system.  What do you mean by
> “built-in commands”?

The pipeline first searches in all the installed packages and matching
the name guile-2 then outputs only the complete name.
Then 'dpkg -L' lists all the files that the package has installed, and
perl filters only the filename ending by .scm.
Last, ctags indexes. :-)

Basically, the 'aptitude | dpkg | perl' feeds 'ctags' with all .scm
files that you can find there [1] and there [2].

[1] https://packages.debian.org/fr/buster/amd64/guile-2.2-dev/filelist
[2] https://packages.debian.org/fr/buster/amd64/guile-2.2-libs/filelist


Note that first 'dpkg -L' is not working if the package is not
installed and second that one can want to install the Vim pluggin
without wanting to install all the Guile toolsuite in their own
profiles.

I am sure you will come up with a more elegant trick for Guix via a
Guile script. :-)


Hope that helps.

Cheers,
simon



  reply	other threads:[~2020-01-29 20:29 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-01-29 15:56 scheme with vim Marc Chantreux
2020-01-29 18:34 ` Ricardo Wurmus
2020-01-29 20:29   ` zimoun [this message]
2020-01-29 20:53     ` Marc Chantreux
2020-01-29 21:04       ` zimoun
2020-02-05 12:58 ` Ricardo Wurmus
2020-02-05 14:26   ` Marc Chantreux
2020-02-05 13:08 ` Ricardo Wurmus
2020-02-05 13:26   ` zimoun
2020-02-05 13:52     ` Marc Chantreux
2020-02-05 15:39       ` zimoun
2020-02-05 16:56         ` Eli Zaretskii
2020-02-05 13:49   ` Marc Chantreux

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://www.gnu.org/software/guile/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CAJ3okZ0CKggE6UEen5m2ZKtPOhincZMd5pmoUWH+0jUyCeR0gQ@mail.gmail.com \
    --to=zimon.toutoune@gmail.com \
    --cc=guile-user@gnu.org \
    --cc=julien@lepiller.eu \
    --cc=rekado@elephly.net \
    /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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).