Re: [Nix-dev] Import remote packages in NixOps/NixOS

[Eric Sagnes]

Thank you, it works perfectly with the `{}` at the end of the import!

On Tue, Mar 08, 2016 at 05:24:02PM +0100, Rok Garbas wrote:
> Hi,
> 
> On Tue, Mar 8, 2016 at 6:42 AM, Eric Sagnes  wrote:
> > It is possible to import foreign modules in NixOps by doing:
> >
> > ```
> > {
> >   network.description = "Web server";
> >
> >   webserver = { config, pkgs, ... }:
> > let
> >   myModuleSrc = (import  {}).fetchFromGitHub {
> >   owner  = "me";
> >   repo   = "myModule";
> >   rev= "v1.0";
> >   sha256 = "";
> >   };
> > in
> > {
> >   imports = [ "${myModuleSrc}/module.nix" ];
> >   services.myModule.enable = true;
> > };
> > }
> > ```
> >
> > Presupposing that the remote package provides a nix build expression,
> > is it possible to directly import it in a similar way?
> > Pseudo code that is not working:
> >
> > ```
> > {
> >   network.description = "Web server";
> >
> >   webserver = { config, pkgs, ... }:
> > let
> >   myPackageSrc = (import  {}).fetchFromGitHub {
> >   owner  = "me";
> >   repo   = "myPackage";
> >   rev= "v1.0";
> >   sha256 = "";
> >   };
> > in
> > {
> >   environment.systemPackages = [
> > (import "${myPackageSrc}/release.nix")
> >   ];
> >
> > };
> > }
> > ```
> >
> > (The above complains about coercing a function to a string.)
> >
> 
> 
> you can also just use builtins.fetchFromTarball.
> 
> for above you probably will want to do
> 
>   (import "${myPackagesSrc}/release.nix" { ... })
> 
> 
> -- 
> Rok Garbas - https://.garbas.si

-- 
Eric Sagnes
サニエ エリック
___
nix-dev mailing list
nix-dev@lists.science.uu.nl
http://lists.science.uu.nl/mailman/listinfo/nix-dev

Re: [Nix-dev] Open source team messaging: mattermost

[Roger Qiu]

As a workaround you can use sameroom.io. I connect to the IRC from Slack
there.
On 09/03/2016 1:20 AM, "Wout Mertens"  wrote:

> That one requires action on the part of the user, unlike the newfangled
> group chat tools, but ok.
>
> On Tue, Mar 8, 2016 at 3:16 PM Herwig Hochleitner 
> wrote:
>
>> 2016-03-08 15:11 GMT+01:00 Wout Mertens :
>>
>>> ok, then how about at the very least an IRC bot that sends you a recent
>>> history when you connect, and that lets you search the logs?
>>>
>>> I presume such a bot must exist?
>>>
>>
>> https://botbot.me/freenode/nixos/
>>
>> --
>
> Wout.
> (typed on mobile, excuse terseness)
>
> ___
> nix-dev mailing list
> nix-dev@lists.science.uu.nl
> http://lists.science.uu.nl/mailman/listinfo/nix-dev
>
>
___
nix-dev mailing list
nix-dev@lists.science.uu.nl
http://lists.science.uu.nl/mailman/listinfo/nix-dev

Re: [Nix-dev] NixOS 16.03 channel available for testing

[Thomas Hunger]

Hm, those images don't boot. I think I picked up the wrong version of
nixpkgs from the environment despite following [1] pretty
meticulously. Apologies if you already tried them.


[1]
https://nixos.org/wiki/NixOS_on_Amazon_EC2

On 8 March 2016 at 18:37, Thomas Hunger  wrote:
> I created some ec2 AMIs for testing:
>
> latest commit: 440e2a757a3e8b8e50e931e339c18c0f0ac54e9b
> channel: 16.03-beta
>
> ami-fdb50d8e in eu-west-1
> ami-23d6324c in eu-central-1
> ami-ca4144a0 in us-east-1
> ami-fd46359d in us-west-1
> ami-ab3ad5cb in us-west-2
> ami-4a438b29 in ap-southeast-1
> ami-64f5d407 in ap-southeast-2
>
> (Don't rely on those for production. I will delete them after the
> official images have been released.)
>
> On 7 March 2016 at 12:36, Domen Kožar  wrote:
>> Hi all,
>>
>> 16.03 release channel has been generated, so you're all welcome to test and
>> report any issues:
>>
>> $ nix-channel --add https://nixos.org/channels/nixos-16.03 nixos
>> $ nixos-rebuild switch --upgrade
>>
>> Domen
>>
>> ___
>> nix-dev mailing list
>> nix-dev@lists.science.uu.nl
>> http://lists.science.uu.nl/mailman/listinfo/nix-dev
>>
___
nix-dev mailing list
nix-dev@lists.science.uu.nl
http://lists.science.uu.nl/mailman/listinfo/nix-dev

Re: [Nix-dev] NixOS 16.03 channel available for testing

[Thomas Hunger]

I created some ec2 AMIs for testing:

latest commit: 440e2a757a3e8b8e50e931e339c18c0f0ac54e9b
channel: 16.03-beta

ami-fdb50d8e in eu-west-1
ami-23d6324c in eu-central-1
ami-ca4144a0 in us-east-1
ami-fd46359d in us-west-1
ami-ab3ad5cb in us-west-2
ami-4a438b29 in ap-southeast-1
ami-64f5d407 in ap-southeast-2

(Don't rely on those for production. I will delete them after the
official images have been released.)

On 7 March 2016 at 12:36, Domen Kožar  wrote:
> Hi all,
>
> 16.03 release channel has been generated, so you're all welcome to test and
> report any issues:
>
> $ nix-channel --add https://nixos.org/channels/nixos-16.03 nixos
> $ nixos-rebuild switch --upgrade
>
> Domen
>
> ___
> nix-dev mailing list
> nix-dev@lists.science.uu.nl
> http://lists.science.uu.nl/mailman/listinfo/nix-dev
>
___
nix-dev mailing list
nix-dev@lists.science.uu.nl
http://lists.science.uu.nl/mailman/listinfo/nix-dev

Re: [Nix-dev] Import remote packages in NixOps/NixOS

[Rok Garbas]

Hi,

On Tue, Mar 8, 2016 at 6:42 AM, Eric Sagnes  wrote:
> It is possible to import foreign modules in NixOps by doing:
>
> ```
> {
>   network.description = "Web server";
>
>   webserver = { config, pkgs, ... }:
> let
>   myModuleSrc = (import  {}).fetchFromGitHub {
>   owner  = "me";
>   repo   = "myModule";
>   rev= "v1.0";
>   sha256 = "";
>   };
> in
> {
>   imports = [ "${myModuleSrc}/module.nix" ];
>   services.myModule.enable = true;
> };
> }
> ```
>
> Presupposing that the remote package provides a nix build expression,
> is it possible to directly import it in a similar way?
> Pseudo code that is not working:
>
> ```
> {
>   network.description = "Web server";
>
>   webserver = { config, pkgs, ... }:
> let
>   myPackageSrc = (import  {}).fetchFromGitHub {
>   owner  = "me";
>   repo   = "myPackage";
>   rev= "v1.0";
>   sha256 = "";
>   };
> in
> {
>   environment.systemPackages = [
> (import "${myPackageSrc}/release.nix")
>   ];
>
> };
> }
> ```
>
> (The above complains about coercing a function to a string.)
>


you can also just use builtins.fetchFromTarball.

for above you probably will want to do

  (import "${myPackagesSrc}/release.nix" { ... })


-- 
Rok Garbas - https://.garbas.si
___
nix-dev mailing list
nix-dev@lists.science.uu.nl
http://lists.science.uu.nl/mailman/listinfo/nix-dev

Re: [Nix-dev] Displaying package parameters

[Fabian Schmitthenner]

I've added a few features:

- Search in 15.09 as well as 16.03
- Search in parameters
- A few more packages with parameters are recognized, e. g. firefox now
shows parameters
- Better error handling: If a parameter fails while trying to determine
what kind it is, it's simply not displayed, but anything else is

As before, demo can be foud here:
http://schmitthenner.eu/nixos-homepage/nixos/packages.html. (compare to
official version: https://nixos.org/nixos/packages.html). You might need
to clear your cache to see the new version.

I've also added a pull request:
https://github.com/NixOS/nixos-homepage/pull/78. Feel free to comment
either on the list or on github.

Have a great day!

Fabian

On 02/29/2016 03:59 AM, Fabian Schmitthenner wrote:
> Hi!
> 
> I just wanted to share that I tried displaying package parameters on the
> nixos homepage and the current result can be seen here:
> http://schmitthenner.eu/nixos-homepage/nixos/packages.html.
> 
> When you click on a package, you hopefully see its parameter. This uses
> a heruristic to try to figure out which parameters are packages (and
> thus not displayed) and which are not (and thus displayed) that goes
> roughly as follows:
> 
> - If the parameter is instantiated - either implicitly or explicitly -
> by callPackage, we look at the value and if it's a derivation, or a list
> or attrset set of derivations, or a function it's not displayed
> - Otherwise, it's displayed
> 
> I think there was a discussion about this a short while ago, but I
> couldn't find it.
> 
> Please let me know what you think and if we might want a (more elaborate
> version, e. g. also displaying the value of default arguments that
> aren't changed by callPackage, which requires an other change to nix
> because this info is currently not available, we only know if the
> argument is optional or not afaik) of this on our official website.
> 
> Source code can be found on
> https://github.com/NixOS/nixos-homepage/compare/master...fkz:master
> Technically, I patched nixpkgs customization, so we not only get the
> override... functions, but also the original parameters and the original
> function.
> Furthermore, this uses a patched version of nix which allows catching
> errors inside nix (added a primop __catch) that also seems useful more
> generally (when polished) (see https://github.com/fkz/nix/tree/catch-throw).
> 
> Fabian
> 
___
nix-dev mailing list
nix-dev@lists.science.uu.nl
http://lists.science.uu.nl/mailman/listinfo/nix-dev

Re: [Nix-dev] Open source team messaging: mattermost

[Matthias Beyer]

On 08-03-2016 15:13:09, Arseniy Seroka wrote:
> Main argument against this proposal was already said: "There are *no* valid
> reasons to split the community.".

Exactly!

-- 
Mit freundlichen Grüßen,
Kind regards,
Matthias Beyer

Proudly sent with mutt.
Happily signed with gnupg.


signature.asc
Description: PGP signature
___
nix-dev mailing list
nix-dev@lists.science.uu.nl
http://lists.science.uu.nl/mailman/listinfo/nix-dev

Re: [Nix-dev] Open source team messaging: mattermost

[Graham Christensen]

Hi Wout,

Would https://botbot.me/freenode/nixos/ do the trick?

Best,
Graham

On 03/08/2016 08:11 AM, Wout Mertens wrote:
ok, then how about at the very least an IRC bot that sends you a 
recent history when you connect, and that lets you search the logs?


I presume such a bot must exist?

Wout.

On Tue, Mar 8, 2016 at 1:32 PM Jonn Mostovoy > wrote:


Dear Wout,

you can't grep discord. Search there is atrocious.
Slack, on the other hand has an amazing full text search engine,
which is a huge part in its success.
However, as search over slack has some heuristics, when I need
plain dumb (or pretty elaborate) grep, I can't run it over history
of Slack.

Picking the tool is about engineering tradeoffs. Right now, IRC is
optimal given optimization parameters, starting from not sharding
the community, going through network resilience and system's fault
tolerance, ending with the degree of democracy IRC provides.

On Mar 8, 2016 7:30 AM, "Wout Mertens" > wrote:

After having used Slack and Discord for a while, I can tell
you that having the recent chat log available with a quick
scroll up is very handy. Conversations can continue over a
longer period of time.

With IRC, you have to open your client, fire off your question
a few times and hope that someone will know the answer
eventually. I can't have IRC open at work all day.


On Fri, Mar 4, 2016 at 12:55 AM Profpatsch > wrote:

On 16-03-01 11:46pm, Teo Klestrup Röijezon wrote:
> Plain IRC sucks.

It’s true, but it f* works.

Especially for developers, devs who can’t configure an IRC
client?
Are those people devs?

But I know the pain.

Hm, we even use IRC as main communication tool in our
Hackerspace,
and so far even non-tech people managed to get a basic
setup running.
Maybe no bouncer, but that’s not required strictly speaking.

--
Proudly written in Mutt with Vim on NixOS.
Q: Why is this email five sentences or less?
A: http://five.sentenc.es
May take up to five days to read your message. If it’s
urgent, call me.

-- 


Wout.
(typed on mobile, excuse terseness)


___
nix-dev mailing list
nix-dev@lists.science.uu.nl 
http://lists.science.uu.nl/mailman/listinfo/nix-dev

--

Wout.
(typed on mobile, excuse terseness)



___
nix-dev mailing list
nix-dev@lists.science.uu.nl
http://lists.science.uu.nl/mailman/listinfo/nix-dev


___
nix-dev mailing list
nix-dev@lists.science.uu.nl
http://lists.science.uu.nl/mailman/listinfo/nix-dev

Re: [Nix-dev] Open source team messaging: mattermost

[Herwig Hochleitner]

2016-03-08 15:20 GMT+01:00 Wout Mertens :

> That one requires action on the part of the user
>

I wouldn't appreciate a bot spamming me on channel entry and I doubt that
IRC can be retrofitted to behave like group chat.


> unlike the newfangled group chat tools, but ok.
>

To me, those are all pretty much DOA and I hope they all burn.
Not that I'm opposed to the idea of persistent history (quite contrary),
but the world really doesn't need another centralized chat protocol. As
soon as there is a proper p2p chat, based on WebRTC, with persistent
history based on a DHT, I'm game.
___
nix-dev mailing list
nix-dev@lists.science.uu.nl
http://lists.science.uu.nl/mailman/listinfo/nix-dev

Re: [Nix-dev] Open source team messaging: mattermost

[Profpatsch]

On 16-03-08 06:30am, Wout Mertens wrote:
> With IRC, you have to open your client, fire off your question a few times
> and hope that someone will know the answer eventually. I can't have IRC
> open at work all day.

You haven't heard of bouncers? ZNC for example.
If as a developer you run an IRC client on your laptop (and only there)
you are doing something wrong.

Btw. I don’t even use a bouncer. mosh, tmux & weechat are probably
the lowest maintenance toolset I know of, and everything automatically
reconnects after the network goes back up. Dedicated machines are as low
as 6.99€/month at the moment.

-- 
Proudly written in Mutt with Vim on NixOS.
Q: Why is this email five sentences or less?
A: http://five.sentenc.es
May take up to five days to read your message. If it’s urgent, call me.
___
nix-dev mailing list
nix-dev@lists.science.uu.nl
http://lists.science.uu.nl/mailman/listinfo/nix-dev

Re: [Nix-dev] Open source team messaging: mattermost

[Wout Mertens]

That one requires action on the part of the user, unlike the newfangled
group chat tools, but ok.

On Tue, Mar 8, 2016 at 3:16 PM Herwig Hochleitner 
wrote:

> 2016-03-08 15:11 GMT+01:00 Wout Mertens :
>
>> ok, then how about at the very least an IRC bot that sends you a recent
>> history when you connect, and that lets you search the logs?
>>
>> I presume such a bot must exist?
>>
>
> https://botbot.me/freenode/nixos/
>
> --

Wout.
(typed on mobile, excuse terseness)
___
nix-dev mailing list
nix-dev@lists.science.uu.nl
http://lists.science.uu.nl/mailman/listinfo/nix-dev

Re: [Nix-dev] Open source team messaging: mattermost

[Herwig Hochleitner]

2016-03-08 15:11 GMT+01:00 Wout Mertens :

> ok, then how about at the very least an IRC bot that sends you a recent
> history when you connect, and that lets you search the logs?
>
> I presume such a bot must exist?
>

https://botbot.me/freenode/nixos/
___
nix-dev mailing list
nix-dev@lists.science.uu.nl
http://lists.science.uu.nl/mailman/listinfo/nix-dev

[Nix-dev] Fwd: [nixpkgs] libreoffice spellcheck gb uk (#13046)

[Wout Mertens]

Anybody have an idea why libreoffice might not find dictionaries on
non-nixos installs?

-- Forwarded message -
From: tomjridge 
Date: Tue, Mar 8, 2016 at 12:22 PM
Subject: Re: [nixpkgs] libreoffice spellcheck gb uk (#13046)
To: NixOS/nixpkgs 
Cc: Wout Mertens 


nix-env -qa '*' |grep myspell
myspell-dict-he-1.1
myspell-dict-he-1.1

I don't know hebrew :(

On ubuntu, installing libreoffice and myspell-en-gb and possibly
libreoffice-l10n-uk worked.

Removing libreoffice and installing nix libreoffice, spell check also
worked (presumably picking up myspell from ubuntu).

HTH

—
Reply to this email directly or view it on GitHub
.
-- 

Wout.
(typed on mobile, excuse terseness)
___
nix-dev mailing list
nix-dev@lists.science.uu.nl
http://lists.science.uu.nl/mailman/listinfo/nix-dev

Re: [Nix-dev] Open source team messaging: mattermost

[Wout Mertens]

ok, then how about at the very least an IRC bot that sends you a recent
history when you connect, and that lets you search the logs?

I presume such a bot must exist?

Wout.

On Tue, Mar 8, 2016 at 1:32 PM Jonn Mostovoy  wrote:

> Dear Wout,
>
> you can't grep discord. Search there is atrocious.
> Slack, on the other hand has an amazing full text search engine, which is
> a huge part in its success.
> However, as search over slack has some heuristics, when I need plain dumb
> (or pretty elaborate) grep, I can't run it over history of Slack.
>
> Picking the tool is about engineering tradeoffs. Right now, IRC is optimal
> given optimization parameters, starting from not sharding the community,
> going through network resilience and system's fault tolerance, ending with
> the degree of democracy IRC provides.
> On Mar 8, 2016 7:30 AM, "Wout Mertens"  wrote:
>
>> After having used Slack and Discord for a while, I can tell you that
>> having the recent chat log available with a quick scroll up is very handy.
>> Conversations can continue over a longer period of time.
>>
>> With IRC, you have to open your client, fire off your question a few
>> times and hope that someone will know the answer eventually. I can't have
>> IRC open at work all day.
>>
>>
>> On Fri, Mar 4, 2016 at 12:55 AM Profpatsch  wrote:
>>
>>> On 16-03-01 11:46pm, Teo Klestrup Röijezon wrote:
>>> > Plain IRC sucks.
>>>
>>> It’s true, but it f* works.
>>>
>>> Especially for developers, devs who can’t configure an IRC client?
>>> Are those people devs?
>>>
>>> But I know the pain.
>>>
>>> Hm, we even use IRC as main communication tool in our Hackerspace,
>>> and so far even non-tech people managed to get a basic setup running.
>>> Maybe no bouncer, but that’s not required strictly speaking.
>>>
>>> --
>>> Proudly written in Mutt with Vim on NixOS.
>>> Q: Why is this email five sentences or less?
>>> A: http://five.sentenc.es
>>> May take up to five days to read your message. If it’s urgent, call me.
>>>
>> --
>>
>> Wout.
>> (typed on mobile, excuse terseness)
>>
>> ___
>> nix-dev mailing list
>> nix-dev@lists.science.uu.nl
>> http://lists.science.uu.nl/mailman/listinfo/nix-dev
>>
>> --

Wout.
(typed on mobile, excuse terseness)
___
nix-dev mailing list
nix-dev@lists.science.uu.nl
http://lists.science.uu.nl/mailman/listinfo/nix-dev

Re: [Nix-dev] Open source team messaging: mattermost

[Jonn Mostovoy]

Dear Wout,

you can't grep discord. Search there is atrocious.
Slack, on the other hand has an amazing full text search engine, which is a
huge part in its success.
However, as search over slack has some heuristics, when I need plain dumb
(or pretty elaborate) grep, I can't run it over history of Slack.

Picking the tool is about engineering tradeoffs. Right now, IRC is optimal
given optimization parameters, starting from not sharding the community,
going through network resilience and system's fault tolerance, ending with
the degree of democracy IRC provides.
On Mar 8, 2016 7:30 AM, "Wout Mertens"  wrote:

> After having used Slack and Discord for a while, I can tell you that
> having the recent chat log available with a quick scroll up is very handy.
> Conversations can continue over a longer period of time.
>
> With IRC, you have to open your client, fire off your question a few times
> and hope that someone will know the answer eventually. I can't have IRC
> open at work all day.
>
>
> On Fri, Mar 4, 2016 at 12:55 AM Profpatsch  wrote:
>
>> On 16-03-01 11:46pm, Teo Klestrup Röijezon wrote:
>> > Plain IRC sucks.
>>
>> It’s true, but it f* works.
>>
>> Especially for developers, devs who can’t configure an IRC client?
>> Are those people devs?
>>
>> But I know the pain.
>>
>> Hm, we even use IRC as main communication tool in our Hackerspace,
>> and so far even non-tech people managed to get a basic setup running.
>> Maybe no bouncer, but that’s not required strictly speaking.
>>
>> --
>> Proudly written in Mutt with Vim on NixOS.
>> Q: Why is this email five sentences or less?
>> A: http://five.sentenc.es
>> May take up to five days to read your message. If it’s urgent, call me.
>>
> --
>
> Wout.
> (typed on mobile, excuse terseness)
>
> ___
> nix-dev mailing list
> nix-dev@lists.science.uu.nl
> http://lists.science.uu.nl/mailman/listinfo/nix-dev
>
>
___
nix-dev mailing list
nix-dev@lists.science.uu.nl
http://lists.science.uu.nl/mailman/listinfo/nix-dev

Re: [Nix-dev] Open source team messaging: mattermost

[Arseniy Seroka]

Main argument against this proposal was already said: "There are *no* valid 
reasons to split the community.".

-- 
Sincerely,
Arseniy Seroka



On 8 March 2016 15:11:10 Kosyrev Serge <_deepf...@feelingofgreen.ru> wrote:

> Matthias Beyer  writes:
>> On 01-03-2016 14:25:23, Jonn Mostovoy wrote:
>>> Tomasz, these all are not valid reasons to split the community.
>>> There are *no* valid reasons to split the community.
>>
>> +1. I'm not willing to switch to some
>>
>>> slack is [...] proprietary
>>
>> thing that I have to register or give away my freedom for.
>
> The thing is, mattermost, from the original proposal, is open source.
>
> If a mattermost instance for the Nix community is set up, you wouldn't
> have to give your registration data to untrusted people, or give up any
> freedoms.
>
> --
> с уважениeм / respectfully,
> Косырев Сергей
> ___
> nix-dev mailing list
> nix-dev@lists.science.uu.nl
> http://lists.science.uu.nl/mailman/listinfo/nix-dev


___
nix-dev mailing list
nix-dev@lists.science.uu.nl
http://lists.science.uu.nl/mailman/listinfo/nix-dev

Re: [Nix-dev] Open source team messaging: mattermost

[Matthias Beyer]

On 01-03-2016 14:25:23, Jonn Mostovoy wrote:
> Tomasz, these all are not valid reasons to split the community.
> There are *no* valid reasons to split the community.

+1. I'm not willing to switch to some

> slack is [...] proprietary

thing that I have to register or give away my freedom for.

-- 
Mit freundlichen Grüßen,
Kind regards,
Matthias Beyer

Proudly sent with mutt.
Happily signed with gnupg.


signature.asc
Description: PGP signature
___
nix-dev mailing list
nix-dev@lists.science.uu.nl
http://lists.science.uu.nl/mailman/listinfo/nix-dev

Re: [Nix-dev] Empty string in single quotes

[Christian Theune]

binwQeGTuyTjG.bin
Description: PGP/MIME Versions Identification


encrypted.asc
Description: OpenPGP encrypted message
___
nix-dev mailing list
nix-dev@lists.science.uu.nl
http://lists.science.uu.nl/mailman/listinfo/nix-dev

Re: [Nix-dev] Empty string in single quotes

[Christian Theune]

Hi,

there’s a short paragraph in the manual:

https://nixos.org/nix/manual/#idm46912467695696 


The result would be:
‘'
‘’'
‘'

A single quote is used to quoute two-single-quotes. I had to read this thrice, 
too. :)

Christian

> On 08 Mar 2016, at 10:24, Игорь Пашев  wrote:
> 
> Hi all.
> 
> 
> How can I write an empty string between single quotes
> when using two single quotes syntax?
> 
> This does the trick:
> ''
> ${"''"}
> ''
> 
> Where is the best place to ask or to find answer for such questions?
> ___
> nix-dev mailing list
> nix-dev@lists.science.uu.nl
> http://lists.science.uu.nl/mailman/listinfo/nix-dev

--
Christian Theune · c...@flyingcircus.io · +49 345 219401 0
Flying Circus Internet Operations GmbH · http://flyingcircus.io
Forsterstraße 29 · 06112 Halle (Saale) · Deutschland
HR Stendal HRB 21169 · Geschäftsführer: Christian. Theune, Christian. Zagrodnick



signature.asc
Description: Message signed with OpenPGP using GPGMail
___
nix-dev mailing list
nix-dev@lists.science.uu.nl
http://lists.science.uu.nl/mailman/listinfo/nix-dev

[Nix-dev] Empty string in single quotes

[Игорь Пашев]

Hi all.


How can I write an empty string between single quotes
when using two single quotes syntax?

This does the trick:
''
${"''"}
''

Where is the best place to ask or to find answer for such questions?
___
nix-dev mailing list
nix-dev@lists.science.uu.nl
http://lists.science.uu.nl/mailman/listinfo/nix-dev