From: Alex Kost <alezost@gmail.com>
To: ng0 <contact.ng0@cryptolab.net>
Cc: guix-devel@gnu.org
Subject: Re: [PATCH] gnu: Add emacs-sx.
Date: Thu, 19 Jan 2017 13:11:19 +0300 [thread overview]
Message-ID: <87efzz4awo.fsf@gmail.com> (raw)
In-Reply-To: <87ziiotwku.fsf@wasp.i-did-not-set--mail-host-address--so-tickle-me> (ng0's message of "Wed, 18 Jan 2017 11:51:45 +0000")
ng0 (2017-01-18 11:51 +0000) wrote:
> Alex Kost <alezost@gmail.com> writes:
>
>> ng0 (2017-01-15 21:10 +0000) wrote:
>>
>>> From: ng0 <ng0@we.make.ritual.n0.is>
>>>
>>> * gnu/packages/emacs.scm (emacs-sx): New variable.
>>
>> Thanks, I committed it as 899bcad310. See the comments below.
>>
>>> ---
>>> gnu/packages/emacs.scm | 26 +++++++++++++++++++++++++-
>>> 1 file changed, 25 insertions(+), 1 deletion(-)
>>>
>>> diff --git a/gnu/packages/emacs.scm b/gnu/packages/emacs.scm
>>> index 50cea7685..ca038bcb2 100644
>>> --- a/gnu/packages/emacs.scm
>>> +++ b/gnu/packages/emacs.scm
>>> @@ -12,7 +12,7 @@
>>> ;;; Copyright © 2016 David Thompson <davet@gnu.org>
>>> ;;; Copyright © 2016 Matthew Jordan <matthewjordandevops@yandex.com>
>>> ;;; Copyright © 2016 Roel Janssen <roel@gnu.org>
>>> -;;; Copyright © 2016 ng0 <ng0@we.make.ritual.n0.is>
>>> +;;; Copyright © 2016, 2017 ng0 <contact.ng0@cryptolab.net>
>>
>> So are you going to use this email now? ".mailmap" still prefers
>> <ng0@libertad.pw>.
>
> I am slowly fading out the use of my own domains as I see no
> point in paying money for names. Yesterday I have switched all
> the gnu.org lists to this email. The commits still happen with
> the @libertad.pw adress, I see the copyright lines as contact
> information. Some people I know don't use email addresses for
> commits for example.
> I will update the .mailmap later this year, at the point where I
> make my commits with this email address.
> Older commits I am working on for some time now still carry
> various other emails, like the one you commited with emacs-sx.
OK. Thanks for letting us know.
[...]
>>> + (sha256
>>> + (base32
>>> + "1w0xghfljqg31axcnv8gzlrd8pw25nji6idnrhflq0af9qh1dw03"))))
>>> + (build-system emacs-build-system)
>>> + (inputs
>>> + `(("emacs-markdown-mode" ,emacs-markdown-mode)
>>> + ("let-alist" ,let-alist)))
>>
>> All emacs dependencies should be propagated, otherwise the package will
>> not work.
>
> Okay, I did not know that. Does the importer know about this?
Yes, since
http://git.savannah.gnu.org/cgit/guix.git/commit/?id=681a555b837d766848baacbed5750e9d30314709
>>> + (home-page "https://github.com/vermiculus/sx.el/")
>>> + (synopsis "Emacs StackExchange client")
>>> + (description
>>> + "Emacs StackExchange client. Ask and answer questions on
>>> +Stack Overflow, Super User, and other StackExchange sites.")
>>> + (license license:gpl3+)))
>>> +
>>> (define-public emacs-f
>>> (package
>>> (name "emacs-f")
>>
>> Also for those who may wonder, there are a lot of errors like this:
>>
>> sx-method.el:33:1:Error: Creating directory: No such file or directory, /homeless-shelter/.emacs.d/.sx
>>
>> This leads to many uncompiled elisp files. This issue is fixed in
>> master so it should be OK in the next release:
>>
>> https://github.com/vermiculus/sx.el/commit/53816e1885df22391ecc820297c1fe7cd381a630
>
> Did this occur when using the application? For me it worked, but
> I have no StackExchange account, so I just searched and read a
> bit, and no errors occured.
All I wanted to say is that multiple elisp files were not compiled (look
at the build log¹ to see the errors I mentioned). Missing ".elc" files
can't make an emacs package fail in any way, it will still work but
using ".el" files instead of ".elc".
¹ http://hydra.gnu.org/build/1817230/log/raw
--
Alex
prev parent reply other threads:[~2017-01-19 10:11 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-15 2:33 Emacs SX (Stackexchange Mode) ng0
2017-01-15 2:33 ` [PATCH] gnu: Add emacs-sx ng0
2017-01-15 19:04 ` Alex Kost
2017-01-15 20:28 ` ng0
2017-01-15 21:10 ` emacs-sx ,v2 ng0
2017-01-15 21:10 ` [PATCH] gnu: Add emacs-sx ng0
2017-01-18 10:03 ` Alex Kost
2017-01-18 11:51 ` ng0
2017-01-19 10:11 ` Alex Kost [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87efzz4awo.fsf@gmail.com \
--to=alezost@gmail.com \
--cc=contact.ng0@cryptolab.net \
--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 external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.