From: Tobias Geerinckx-Rice <me@tobias.gr>
To: ludo@gnu.org
Cc: 27675@debbugs.gnu.org
Subject: [bug#27675] [PATCH] gnu: kbd: Recursively search $LOADKEYS_KEYMAP_PATH.
Date: Mon, 17 Jul 2017 11:35:42 +0200 [thread overview]
Message-ID: <383b1065-2c96-4982-2fc1-92b356a50838@tobias.gr> (raw)
In-Reply-To: <87poczctc8.fsf@gnu.org>
[-- Attachment #1.1: Type: text/plain, Size: 814 bytes --]
Ludo',
On 17/07/17 11:20, Ludovic Courtès wrote:
> Tobias Geerinckx-Rice <me@tobias.gr> skribis:
>
>> Fix a regression since commit fd7000fe33d3c4188c241cab97e2b891dd4e1268.
<snip>
> That works if you copy paste the suggested search path in a shell, but
> not if we pass it to ‘evaluate-search-paths’ from (guix search-paths)
I'm confused. What exactly doesn't work? Here, after this patch,
LOADKEYS_KEYMAP_PATH contains "**" like it should.
(I wouldn't have been able to install GuixSD if it didn't! :-) Whoever
designed the Belgian keyboard layout was either on some very cheap
crack, or the expensive good stuff.)
> (it doesn’t recognize the ** syntax.)
Hrm. I don't think it should try to recognise anything, that can only be
done at run-time.
Kind regards,
T G-R
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 504 bytes --]
next prev parent reply other threads:[~2017-07-17 9:35 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-13 0:34 [bug#27675] [PATCH] gnu: kbd: Recursively search $LOADKEYS_KEYMAP_PATH Tobias Geerinckx-Rice
2017-07-13 0:41 ` Tobias Geerinckx-Rice
2017-07-13 7:41 ` ng0
2017-07-14 8:39 ` bug#27675: " Tobias Geerinckx-Rice
2017-07-17 9:20 ` [bug#27675] " Ludovic Courtès
2017-07-17 9:35 ` Tobias Geerinckx-Rice [this message]
2017-07-17 11:00 ` Ludovic Courtès
2017-07-17 11:54 ` Tobias Geerinckx-Rice
[not found] ` <1a1b4745-31a4-f32c-ed46-cb7640591aae@tobias.gr>
2017-07-17 15:46 ` Ludovic Courtès
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=383b1065-2c96-4982-2fc1-92b356a50838@tobias.gr \
--to=me@tobias.gr \
--cc=27675@debbugs.gnu.org \
--cc=ludo@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).