From: Brett Gilio <brettg@posteo.net>
To: Leo Prikler <leo.prikler@student.tugraz.at>
Cc: 38463@debbugs.gnu.org
Subject: [bug#38463] [PATCH 3/3] gnu: emacs-telega: Properly install alists.
Date: Thu, 05 Dec 2019 12:00:28 -0600 [thread overview]
Message-ID: <87fthyd54z.fsf@posteo.net> (raw)
In-Reply-To: <3566e38523f0ff4badf50ade8c1498006f1cb872.camel@student.tugraz.at> (Leo Prikler's message of "Thu, 05 Dec 2019 18:31:26 +0100")
Leo Prikler <leo.prikler@student.tugraz.at> writes:
> Out of curiosity, would it be possible to make this a subfolder of the
> telega installation directory? It appears, as though these files are
> accessed via telega-etc-file in telega-util.el, so it should still
> function in the same way with the right substitutions.
>
> Regards,
> Leo
>
Hi Leo,
I want to make sure I understand clearly what you are saying. The telega
installation directory seems to be just the
<profile>/share/emacs/site-lisp. What subdirectory are you speaking of
exactly? I will send a revised patch once I get some more information
:).
Thanks!
--
Brett M. Gilio
https://git.sr.ht/~brettgilio/
next prev parent reply other threads:[~2019-12-05 18:01 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-02 21:33 [bug#38463] [PATCH] Telega test suite and change in revision Brett Gilio
2019-12-02 21:34 ` [bug#38463] [PATCH 1/2] gnu: emacs-telega: Use test suites Brett Gilio
2019-12-02 21:35 ` [bug#38463] [PATCH 2/2] gnu: emacs-telega: Update to 0.4.4-2 Brett Gilio
2019-12-05 0:36 ` [bug#38463] [PATCH] Telega test suite and change in revision Brett Gilio
2019-12-05 13:50 ` [bug#38463] [PATCH 3/3] gnu: emacs-telega: Properly install alists Brett Gilio
2019-12-05 17:31 ` Leo Prikler
2019-12-05 18:00 ` Brett Gilio [this message]
2019-12-05 18:18 ` Leo Prikler
2019-12-05 18:46 ` Brett Gilio
2019-12-05 22:55 ` Leo Prikler
2019-12-05 20:01 ` [bug#38463] [PATCH 3/3] gnu: emacs-telega: Install telega-data to site-lisp Brett Gilio
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=87fthyd54z.fsf@posteo.net \
--to=brettg@posteo.net \
--cc=38463@debbugs.gnu.org \
--cc=leo.prikler@student.tugraz.at \
/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).