From: ng0 <contact.ng0@cryptolab.net>
To: Ricardo Wurmus <rekado@elephly.net>
Cc: 25741@debbugs.gnu.org
Subject: bug#25741: [PATCH 2/2] gnu: kbd: Add neo layout.
Date: Fri, 28 Apr 2017 09:39:40 +0000 [thread overview]
Message-ID: <20170428093940.qebl5oexqszdblw3@abyayala> (raw)
In-Reply-To: <87d1bxarj4.fsf@elephly.net>
Ricardo Wurmus transcribed 0.5K bytes:
>
> ng0 <contact.ng0@cryptolab.net> writes:
>
> > Alright, here is the reworked version.
> >
> > Because it is equal to the result of the previous one, I am
> > positive that it works like this (the previous version did).
>
> Thanks. This still modifies the kbd package. Have you tried what I
> proposed, namely to install this as a separate package and /somehow/
> make kbd find the installed keymap? It would be nicer than to modify
> the kbd package itself.
>
> --
> Ricardo
>
> GPG: BCA6 89B6 3655 3801 C3C6 2150 197A 5888 235F ACAC
> https://elephly.net
>
Would this still work as intended?
kbd is a global package, part of the base. If I create a new
package which inherits from kbd, and people have to explicitly
add it to (packages) in (operating-system), it will colide with
(kbd). I think this really is the safest solution unless you
can convince me that it will work the way you proposed.
Or am I wrong and all you suggest is that (kbd) simply
finds the neo.map in the store?
I feel like kbd doesn#t work this way, but depending on
your explanation I can try.
--
PGP and more: https://people.pragmatique.xyz/ng0/
next prev parent reply other threads:[~2017-04-28 9:40 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20170215164800.15907-1-contact.ng0@cryptolab.net>
[not found] ` <20170215164800.15907-2-contact.ng0@cryptolab.net>
[not found] ` <8737em3ov0.fsf@elephly.net>
2017-04-27 21:53 ` bug#25741: [PATCH 2/2] gnu: kbd: Add neo layout ng0
2017-04-28 8:02 ` Ricardo Wurmus
2017-04-28 9:39 ` ng0 [this message]
2017-04-28 14:37 ` Ricardo Wurmus
[not found] <20170215164614.lmyymqkagvudqeq6@wasp>
2017-05-25 16:47 ` ng0
2017-05-25 18:17 ` Marius Bakke
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=20170428093940.qebl5oexqszdblw3@abyayala \
--to=contact.ng0@cryptolab.net \
--cc=25741@debbugs.gnu.org \
--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.
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).