From: Eshel Yaron <me@eshelyaron.com>
To: Philip Kaludercic <philipk@posteo.net>
Cc: emacs-devel@gnu.org
Subject: Re: [ELPA] New package: dict
Date: Fri, 12 May 2023 16:32:06 +0300 [thread overview]
Message-ID: <m1lehtwu95.fsf@eshelyaron.com> (raw)
In-Reply-To: <871qjmwwhq.fsf@posteo.net> (Philip Kaludercic's message of "Thu, 11 May 2023 18:31:29 +0000")
[-- Attachment #1: Type: text/plain, Size: 1096 bytes --]
Philip Kaludercic <philipk@posteo.net> writes:
> Eshel Yaron <me@eshelyaron.com> writes:
>
>> Philip Kaludercic <philipk@posteo.net> writes:
>>
>>> Eshel Yaron <me@eshelyaron.com> writes:
>>>
>>>> + (dict :url "git://git.eshelyaron.com/dict.git"
>>>
>>> Do you have any other access method beside git://?
>>
>> For anonymous access, currently no. But I can mirror the repo to
>> Sourcehut from where you can clone it via HTTPS. Would that be more
>> convenient?
>
> That would be good, my understanding is that git:// is not encrypted so
> we should avoid using it if possible.
>>>> + :doc "README.org")
>>>
>>> Should we add a ":readme ignore" to prevent the contents of this file
>>> from also appearing when the user invokes C-h P dict RET ?
>>
>> Sure, in this case would C-h P show the commentary section of dict.el?
>
> Right. Feel free to extend that with pointers, I just think we should
> avoid overwhelming users with the entire documentation if they just want
> to get the basic gist of a package.
Alright, I'm attaching a new patch that addresses both these points.
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: v2-0001-elpa-packages-dict-New-package.patch --]
[-- Type: text/x-patch, Size: 743 bytes --]
From 2466225fd527e3748c266307d6858407011105f5 Mon Sep 17 00:00:00 2001
From: Eshel Yaron <me@eshelyaron.com>
Date: Thu, 11 May 2023 14:20:16 +0300
Subject: [PATCH v2] * elpa-packages (dict): New package
---
elpa-packages | 3 +++
1 file changed, 3 insertions(+)
diff --git a/elpa-packages b/elpa-packages
index d5603f7803..637d71685e 100644
--- a/elpa-packages
+++ b/elpa-packages
@@ -201,6 +201,9 @@
:news "CHANGELOG.org"
:readme "README.md")
(devdocs :url "https://github.com/astoff/devdocs.el")
+ (dict :url "https://git.sr.ht/~eshel/dict"
+ :doc "README.org"
+ :readme ignore)
(dict-tree :url "http://www.dr-qubit.org/git/predictive.git"
:manual-sync t ;; The upstream doesn't exist any more!
)
--
2.40.1
[-- Attachment #3: Type: text/plain, Size: 18 bytes --]
--
Best,
Eshel
next prev parent reply other threads:[~2023-05-12 13:32 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-11 13:22 [ELPA] New package: dict Eshel Yaron
2023-05-11 13:59 ` Eli Zaretskii
2023-05-11 14:14 ` Philip Kaludercic
2023-05-11 17:56 ` Eshel Yaron
2023-05-11 18:16 ` Eli Zaretskii
2023-05-11 18:29 ` Philip Kaludercic
2023-05-12 13:17 ` Eshel Yaron
2023-05-12 13:44 ` Eli Zaretskii
2023-05-14 6:41 ` Eshel Yaron
2023-05-14 9:14 ` Eli Zaretskii
2023-05-15 18:50 ` Eshel Yaron
2023-05-18 7:57 ` Eshel Yaron
2023-05-18 8:32 ` Eli Zaretskii
2023-05-18 10:59 ` Eli Zaretskii
2023-05-18 12:21 ` Eshel Yaron
2023-05-18 14:09 ` Eli Zaretskii
2023-05-18 15:51 ` Eshel Yaron
2023-05-18 15:58 ` Eli Zaretskii
2023-05-19 8:34 ` Eshel Yaron
2023-05-20 14:19 ` Eli Zaretskii
2023-05-20 16:49 ` Philip Kaludercic
2023-05-20 18:27 ` Eshel Yaron
2023-05-20 19:11 ` Philip Kaludercic
2023-05-21 6:52 ` Eshel Yaron
2023-05-25 9:52 ` Eshel Yaron
2023-05-25 19:10 ` Philip Kaludercic
2023-05-26 9:16 ` Eli Zaretskii
2023-05-26 11:36 ` Rudolf Adamkovič
2023-05-26 12:26 ` Eshel Yaron
2023-05-18 12:59 ` Philip Kaludercic
2023-05-18 15:37 ` Eshel Yaron
2023-05-18 15:58 ` Philip Kaludercic
2023-05-14 16:06 ` Stephen Leake
2023-05-15 18:58 ` Eshel Yaron
2023-05-11 14:18 ` Philip Kaludercic
2023-05-11 18:00 ` Eshel Yaron
2023-05-11 18:31 ` Philip Kaludercic
2023-05-12 13:32 ` Eshel Yaron [this message]
2023-05-16 19:38 ` Philip Kaludercic
2023-05-17 2:25 ` Eli Zaretskii
2023-05-13 22:30 ` Richard Stallman
2023-05-14 6:48 ` Eshel Yaron
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=m1lehtwu95.fsf@eshelyaron.com \
--to=me@eshelyaron.com \
--cc=emacs-devel@gnu.org \
--cc=philipk@posteo.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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.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.