zimoun <zimon.toutoune@gmail.com> writes:

>> But for which benefit?  It seems that this single example
>>
>> >>  - guix search bin/gmsh gimp
>>
>> covers all your needs.
>
> No.
>
> For example:
>
>> >>  - guix search file:gmsh.h gimp
>
> I am looking for the file gmsh.h and I do not know nothing more.

--8<---------------cut here---------------start------------->8---
guix search /gmsh.h 
--8<---------------cut here---------------end--------------->8---

would work.  You don't need the full path.

>> >>  - guix search file:ieee*.sty bin/gmsh latex
>
> I know nothing about the path of the file ieee*.sty and it does not
> belong to the package gmsh.

I don't understand what you are trying to search.  Is it the 'bin/gmsh'
file or the files matching 'ieee*.sty'?

>> For advanced search, we could provide "explorable" features with a
>> graphical user interface (which I plan to work on later) or Emacs (a big
>> like `guix-packages-by-name', but more general).  Those interface would
>> allow the user to chain searches by narrowing down lists.  What you
>> print in the end is irrelevant since you can have an interactive
>> presentation (unlike the shell).
>
> ...but at some point you need some semantic for filtering, at least for regexp.

We can have regexp of course, that's not a problem.

-- 
Pierre Neidhardt
https://ambrevar.xyz/