From: Julien Lepiller <julien@lepiller.eu>
To: guix-devel@gnu.org
Subject: Re: my latest blog post
Date: Fri, 08 Jun 2018 11:45:19 +0200 [thread overview]
Message-ID: <a08b8abc8aaf7b035bcce9eec46fee6d@lepiller.eu> (raw)
In-Reply-To: <87602ttye9.fsf@lassieur.org>
Le 2018-06-08 11:34, Clément Lassieur a écrit :
> Hi Julien,
>
> Julien Lepiller <julien@lepiller.eu> writes:
>
>> I read you're having trouble to find information from the section
>> titles. Info
>> manuals
>> have an index where it's easier to find things. But actually, what
>> helps me
>> the most
>> is to ignore the `info` command and open either the full .texi source
>> or the
>> "html
>> in one page" version. Then I can do full-text search, which is a lot
>> quicker. Does
>> anyone know if there is a similar facility in the info program?
>
> Did you try the 's' shortcut?
>
> https://www.gnu.org/software/texinfo/manual/info-stnd/info-stnd.html#Searching-Commands
Ho, nice! Thank you! So 's' or '/' to search, and '{' or '}' to search
previous/next occurence.
That's exactly what I wanted :)
next prev parent reply other threads:[~2018-06-08 9:45 UTC|newest]
Thread overview: 53+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-07 15:25 my latest blog post Catonano
2018-06-07 16:28 ` Joshua Branson
2018-06-08 4:24 ` Christopher Lemmer Webber
2018-06-08 6:18 ` Fis Trivial
2018-06-08 14:02 ` Ricardo Wurmus
2018-06-08 8:25 ` Catonano
2018-06-08 13:51 ` Fis Trivial
2018-06-08 14:25 ` Ricardo Wurmus
2018-06-09 7:47 ` Catonano
2018-06-09 12:24 ` Ricardo Wurmus
2018-06-09 13:07 ` Catonano
2018-06-09 15:29 ` Christopher Lemmer Webber
2018-06-09 13:51 ` Christopher Lemmer Webber
2018-06-07 17:03 ` Mark H Weaver
2018-06-07 19:40 ` Catonano
2018-06-08 9:39 ` Nils Gillmann
2018-06-08 9:45 ` Catonano
2018-06-08 18:05 ` Mark H Weaver
2018-06-09 7:00 ` Catonano
2018-06-09 10:39 ` Ricardo Wurmus
2018-06-09 10:52 ` Catonano
2018-06-09 12:14 ` Ricardo Wurmus
2018-06-09 13:03 ` Catonano
2018-06-10 10:53 ` Mark H Weaver
2018-06-07 18:11 ` Thorsten Wilms
2018-06-07 21:45 ` Alex Vong
2018-06-08 9:15 ` Julien Lepiller
2018-06-08 9:34 ` Clément Lassieur
2018-06-08 9:45 ` Julien Lepiller [this message]
2018-06-08 13:50 ` Widen info Oleg Pykhalov
2018-06-08 13:59 ` Julien Lepiller
2018-06-08 13:49 ` my latest blog post Ludovic Courtès
2018-06-09 5:59 ` Catonano
2018-06-09 22:49 ` myglc2
2018-06-10 0:51 ` Mark H Weaver
2018-06-10 6:55 ` Pjotr Prins
2018-06-10 9:07 ` Catonano
2018-06-10 9:29 ` Ricardo Wurmus
2018-06-10 9:30 ` Catonano
2018-06-10 10:37 ` Ricardo Wurmus
2018-06-10 10:45 ` Mark H Weaver
2018-06-10 12:06 ` Pjotr Prins
2018-06-10 7:58 ` Catonano
2018-06-10 9:26 ` Ricardo Wurmus
2018-06-10 9:27 ` Catonano
2018-06-10 19:13 ` Ludovic Courtès
2018-06-10 8:07 ` Catonano
2018-06-10 19:23 ` Ludovic Courtès
2018-06-10 8:17 ` my latest blog post [everyone, please take a cooldown break] Nils Gillmann
2018-06-10 13:33 ` Christopher Lemmer Webber
2018-06-10 14:18 ` Gábor Boskovits
2018-06-10 14:37 ` Kei Kebreau
2018-06-11 6:01 ` swedebugia
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=a08b8abc8aaf7b035bcce9eec46fee6d@lepiller.eu \
--to=julien@lepiller.eu \
--cc=guix-devel@gnu.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).