GNU bug report logs -
#67272
[PATCH] gnu: Add emacs-zop-to-char.
Previous Next
To add a comment to this bug, you must first unarchive it, by sending
a message to control AT debbugs.gnu.org, with unarchive 67272 in the body.
You can then email your comments to 67272 AT debbugs.gnu.org in the normal way.
Toggle the display of automated, internal messages from the tracker.
Report forwarded
to
andrew <at> trop.in, cox.katherine.e+guix <at> gmail.com, liliana.prikler <at> gmail.com, guix-patches <at> gnu.org
:
bug#67272
; Package
guix-patches
.
(Sun, 19 Nov 2023 09:56:01 GMT)
Full text and
rfc822 format available.
Acknowledgement sent
to
Rostislav Svoboda <rostislav.svoboda <at> gmail.com>
:
New bug report received and forwarded. Copy sent to
andrew <at> trop.in, cox.katherine.e+guix <at> gmail.com, liliana.prikler <at> gmail.com, guix-patches <at> gnu.org
.
(Sun, 19 Nov 2023 09:56:02 GMT)
Full text and
rfc822 format available.
Message #5 received at submit <at> debbugs.gnu.org (full text, mbox):
* gnu/packages/emacs-xyz.scm (emacs-zop-to-char): New variable.
Change-Id: I6307a1c72739f627508886acc4130870913f9e71
---
gnu/packages/emacs-xyz.scm | 21 +++++++++++++++++++++
1 file changed, 21 insertions(+)
diff --git a/gnu/packages/emacs-xyz.scm b/gnu/packages/emacs-xyz.scm
index bad97f436d..c9a4f5674b 100644
--- a/gnu/packages/emacs-xyz.scm
+++ b/gnu/packages/emacs-xyz.scm
@@ -38739,6 +38739,27 @@ (define-public emacs-totp
variations, including non-standard base32 encodings.")
(license license:gpl3+))))
+(define-public emacs-zop-to-char
+ (let ((commit "00152aa666354b27e56e20565f186b363afa0dce")
+ (revision "0"))
+ (package
+ (name "emacs-zop-to-char")
+ (version (git-version "1.1" revision commit))
+ (source
+ (origin
+ (method git-fetch)
+ (uri (git-reference
+ (url "https://github.com/thierryvolpiatto/zop-to-char")
+ (commit commit)))
+ (file-name (git-file-name name version))
+ (sha256
+ (base32 "1s4adi9hyhxn7ynx195mgg10h817hxdmlzlp09633bj0llr1mjn3"))))
+ (build-system emacs-build-system)
+ (home-page "https://github.com/thierryvolpiatto/zop-to-char")
+ (synopsis "A visual zap-to-char command for Emacs")
+ (description "A visual zap-to-char command for Emacs.")
+ (license license:gpl3+))))
+
;;;
;;; Avoid adding new packages to the end of this file. To reduce the chances
;;; of a merge conflict, place them above by existing packages with similar
base-commit: b7abea0fd6a146563830db1dc4ddd0cceb6fcf1c
prerequisite-patch-id: 9a43774d20eb5c5f07500aa283aa501ce7c1d7a8
prerequisite-patch-id: fe772324962c490d954bf6197d82e3152a3990d0
prerequisite-patch-id: a7f5628906b829261dc2bfbe417a7be1eec850ec
prerequisite-patch-id: 9c0c2e59be28a04f226f98bcab6db415d00901a8
prerequisite-patch-id: 02461a5e19d62f02948d363719a7ece122198416
prerequisite-patch-id: 656a9d241ce1e5d445a535f11983ba493f0147b3
prerequisite-patch-id: 6a4d5facca6224cc9d043e39ffa4bcd6d091bed5
prerequisite-patch-id: b4992d2603e1a819e7bb0f9a354d97458b3f80ad
prerequisite-patch-id: fffccc797bda74d3b25e987538ff5b916e0e976f
--
2.41.0
Information forwarded
to
guix-patches <at> gnu.org
:
bug#67272
; Package
guix-patches
.
(Sun, 19 Nov 2023 13:43:02 GMT)
Full text and
rfc822 format available.
Message #8 received at 67272 <at> debbugs.gnu.org (full text, mbox):
Am Sonntag, dem 19.11.2023 um 10:54 +0100 schrieb Rostislav Svoboda:
> * gnu/packages/emacs-xyz.scm (emacs-zop-to-char): New variable.
>
> Change-Id: I6307a1c72739f627508886acc4130870913f9e71
> ---
> gnu/packages/emacs-xyz.scm | 21 +++++++++++++++++++++
> 1 file changed, 21 insertions(+)
>
> diff --git a/gnu/packages/emacs-xyz.scm b/gnu/packages/emacs-xyz.scm
> index bad97f436d..c9a4f5674b 100644
> --- a/gnu/packages/emacs-xyz.scm
> +++ b/gnu/packages/emacs-xyz.scm
> @@ -38739,6 +38739,27 @@ (define-public emacs-totp
> variations, including non-standard base32 encodings.")
> (license license:gpl3+))))
>
> +(define-public emacs-zop-to-char
> + (let ((commit "00152aa666354b27e56e20565f186b363afa0dce")
> + (revision "0"))
> + (package
> + (name "emacs-zop-to-char")
> + (version (git-version "1.1" revision commit))
> + (source
> + (origin
> + (method git-fetch)
> + (uri (git-reference
> + (url
> "https://github.com/thierryvolpiatto/zop-to-char")
> + (commit commit)))
> + (file-name (git-file-name name version))
> + (sha256
> + (base32
> "1s4adi9hyhxn7ynx195mgg10h817hxdmlzlp09633bj0llr1mjn3"))))
> + (build-system emacs-build-system)
> + (home-page "https://github.com/thierryvolpiatto/zop-to-char")
> + (synopsis "A visual zap-to-char command for Emacs")
> + (description "A visual zap-to-char command for Emacs.")
Description a sentence.
> + (license license:gpl3+))))
> +
Cheers
Information forwarded
to
guix-patches <at> gnu.org
:
bug#67272
; Package
guix-patches
.
(Sun, 19 Nov 2023 13:53:02 GMT)
Full text and
rfc822 format available.
Message #11 received at 67272 <at> debbugs.gnu.org (full text, mbox):
> > + (description "A visual zap-to-char command for Emacs.")
> Description a sentence.
???
"Description a sentence" is not a meaningful English sentence.
Cheers
Information forwarded
to
guix-patches <at> gnu.org
:
bug#67272
; Package
guix-patches
.
(Sun, 19 Nov 2023 16:28:02 GMT)
Full text and
rfc822 format available.
Message #14 received at 67272 <at> debbugs.gnu.org (full text, mbox):
Am Sonntag, dem 19.11.2023 um 14:51 +0100 schrieb Rostislav Svoboda:
> > > + (description "A visual zap-to-char command for Emacs.")
> > Description a sentence.
>
> ???
> "Description a sentence" is not a meaningful English sentence.
Excuse my brevity. It should have been "The description of a package
should at least be a meaningful English sentence."
Cheer
Information forwarded
to
guix-patches <at> gnu.org
:
bug#67272
; Package
guix-patches
.
(Sun, 19 Nov 2023 16:29:01 GMT)
Full text and
rfc822 format available.
Message #17 received at 67272 <at> debbugs.gnu.org (full text, mbox):
Am Sonntag, dem 19.11.2023 um 17:27 +0100 schrieb Liliana Marie
Prikler:
> Am Sonntag, dem 19.11.2023 um 14:51 +0100 schrieb Rostislav Svoboda:
> > > > + (description "A visual zap-to-char command for Emacs.")
> > > Description a sentence.
> >
> > ???
> > "Description a sentence" is not a meaningful English sentence.
> Excuse my brevity. It should have been "The description of a package
> should at least be a meaningful English sentence."
>
> Cheer
Missing 's'
Information forwarded
to
guix-patches <at> gnu.org
:
bug#67272
; Package
guix-patches
.
(Sun, 19 Nov 2023 18:39:02 GMT)
Full text and
rfc822 format available.
Message #20 received at 67272 <at> debbugs.gnu.org (full text, mbox):
Hello,
Rostislav Svoboda <rostislav.svoboda <at> gmail.com> writes:
> * gnu/packages/emacs-xyz.scm (emacs-zop-to-char): New variable.
Thank you.
> +(define-public emacs-zop-to-char
> + (let ((commit "00152aa666354b27e56e20565f186b363afa0dce")
> + (revision "0"))
I suggest to use the previous commit, for two reasons :
- it is a tagged commit, so you can set `version' to "1.1" instead of
the ugly (git-version ...) stuff;
- the current commit only adds a donation link to the README.
> + (synopsis "A visual zap-to-char command for Emacs")
The synopsis shouldn't start with an article, here "A".
You may want to use guix lint to double-check this.
Regards,
--
Nicolas Goaziou
Information forwarded
to
guix-patches <at> gnu.org
:
bug#67272
; Package
guix-patches
.
(Sun, 19 Nov 2023 19:03:01 GMT)
Full text and
rfc822 format available.
Message #23 received at 67272 <at> debbugs.gnu.org (full text, mbox):
> - the current commit only adds a donation link to the README.
Actually, the 00152aa deleted the donation link. It didn't add it.
Either way, the commit is about "money", and that's a sensitive thing
so it's better to respect its intention.
Cheers
Information forwarded
to
guix-patches <at> gnu.org
:
bug#67272
; Package
guix-patches
.
(Mon, 20 Nov 2023 07:32:01 GMT)
Full text and
rfc822 format available.
Message #26 received at 67272 <at> debbugs.gnu.org (full text, mbox):
Hello,
Rostislav Svoboda <rostislav.svoboda <at> gmail.com> writes:
>> - the current commit only adds a donation link to the README.
>
> Actually, the 00152aa deleted the donation link. It didn't add it.
OK.
> Either way, the commit is about "money", and that's a sensitive thing
> so it's better to respect its intention.
I disagree. Guix usually sticks to actual releases, unless there's
a really good reason not to, such as a major bug in the last release. In
this situation, the last commit is not even a feature, so it's better to
just package the 1.1 release.
Note that if the last change was that important for the author, they
would have made a release out of it. I don't think Guix would offense
anyone by providing real 1.1.
Regards,
--
Nicolas Goaziou
Information forwarded
to
guix-patches <at> gnu.org
:
bug#67272
; Package
guix-patches
.
(Mon, 20 Nov 2023 09:42:02 GMT)
Full text and
rfc822 format available.
Message #29 received at 67272 <at> debbugs.gnu.org (full text, mbox):
Hello
> I disagree. Guix usually sticks to actual releases [...] Note that if the last change was that important for the author, they would have made a release out of it.
Sticking to actual releases makes sense for packages that follow a
"release-has-a-version" policy, which is common for big & popular
ones.
But there's a number [see below] of smaller, less popular elisp
packages with infrequent contributions where the author doesn't really
bother with a strict "tagged-releases" policy. Sometimes it's
forgotten over the years, so "rolling-releases" become the norm.
IMO that's the case for our
https://github.com/thierryvolpiatto/zop-to-char too. Our 00152aa was
done on May 1, 2018. That's over five years ago. Waiting for 1.2
doesn't make sense. It's probably not happening anytime soon, not even
soon-ish, even though the 00152aa seems to be important.
Cheers
Few examples:
| url | github stars |
last commit | nr of commits | nr of releases |
| https://github.com/007kevin/pdf-view-restore | 34 |
Sep 4, 2019 | 23 | 1 |
| https://github.com/DamienCassou/json-navigator | 129 |
Sep 4, 2023 | 43 | 1 |
| https://github.com/FelipeLema/emacs-counsel-gtags | 22 |
Feb 22, 2021 | 208 | 1 |
| https://github.com/Kungi/helm-cider-history | 2 |
Jul 19, 2015 | 3 | 0 |
| https://github.com/ZehCnaS34/zonokai-emacs | 11 |
Mar 22, 2016 | 130 | 0 |
Information forwarded
to
guix-patches <at> gnu.org
:
bug#67272
; Package
guix-patches
.
(Mon, 20 Nov 2023 10:49:01 GMT)
Full text and
rfc822 format available.
Message #32 received at 67272 <at> debbugs.gnu.org (full text, mbox):
Rostislav Svoboda <rostislav.svoboda <at> gmail.com> writes:
>> I disagree. Guix usually sticks to actual releases [...] Note that if the last change was that important for the author, they would have made a release out of it.
>
> Sticking to actual releases makes sense for packages that follow a
> "release-has-a-version" policy, which is common for big & popular
> ones.
>
> But there's a number [see below] of smaller, less popular elisp
> packages with infrequent contributions where the author doesn't really
> bother with a strict "tagged-releases" policy. Sometimes it's
> forgotten over the years, so "rolling-releases" become the norm.
>
> IMO that's the case for our
> https://github.com/thierryvolpiatto/zop-to-char too. Our 00152aa was
> done on May 1, 2018. That's over five years ago. Waiting for 1.2
> doesn't make sense. It's probably not happening anytime soon, not even
> soon-ish, even though the 00152aa seems to be important.
I already made my point and have nothing to add to that topic.
Regards,
Information forwarded
to
guix-patches <at> gnu.org
:
bug#67272
; Package
guix-patches
.
(Mon, 20 Nov 2023 12:28:02 GMT)
Full text and
rfc822 format available.
Message #35 received at 67272 <at> debbugs.gnu.org (full text, mbox):
[Message part 1 (text/plain, inline)]
Hello,
> > + (description "A visual zap-to-char command for Emacs.")
> "The description of a package should at least be a meaningful English sentence."
The original zap-to-char doesn't provide much. The enhancement - our
zop-to-char doesn't improve the situation either.
The same goes for zap-up-to-char and zop-up-to-char. So asking me to
come up with one is... sigh, anyway here you go.
> > + (synopsis "A visual zap-to-char command for Emacs")
> The synopsis shouldn't start with an article, here "A".
Fixed. Sorryyyyyyyy.
> You may want to use guix lint to double-check this.
I did and... hmm looks like it's time to visit the ophthalmologist again.
I reworked the patch and I'm resending it in the attachment.
Cheers
[0001-gnu-Add-emacs-zop-to-char.patch (text/x-patch, attachment)]
Information forwarded
to
guix-patches <at> gnu.org
:
bug#67272
; Package
guix-patches
.
(Mon, 20 Nov 2023 12:30:02 GMT)
Full text and
rfc822 format available.
Message #38 received at 67272 <at> debbugs.gnu.org (full text, mbox):
> I already made my point and have nothing to add to that topic.
So have I, and neither do I.
Cheers
Information forwarded
to
guix-patches <at> gnu.org
:
bug#67272
; Package
guix-patches
.
(Mon, 20 Nov 2023 19:25:02 GMT)
Full text and
rfc822 format available.
Message #41 received at 67272 <at> debbugs.gnu.org (full text, mbox):
Am Montag, dem 20.11.2023 um 13:26 +0100 schrieb Rostislav Svoboda:
> +(define-public emacs-zop-to-char
> + (let ((commit "00152aa666354b27e56e20565f186b363afa0dce")
> + (revision "0"))
> + (package
> + (name "emacs-zop-to-char")
> + (version (git-version "1.1" revision commit))
> + (source
> + (origin
> + (method git-fetch)
> + (uri (git-reference
> + (url
> "https://github.com/thierryvolpiatto/zop-to-char")
> + (commit commit)))
> + (file-name (git-file-name name version))
> + (sha256
> + (base32
> "1s4adi9hyhxn7ynx195mgg10h817hxdmlzlp09633bj0llr1mjn3"))))
> + (build-system emacs-build-system)
> + (home-page "https://github.com/thierryvolpiatto/zop-to-char")
> + (synopsis "Visual @code{zap-to-char}-related commands for
> Emacs")
> + (description
> + "Visually enhanced versions of @code{zap-to-char} and
> +@code{zap-to-up-char}.
Still not sentence.
> Precise character-level navigation and editing across the
> +buffer, facilitating efficient deletion, replacement, and jumping to
> specific
> +locations.")
Not sentence either.
Cheers
Information forwarded
to
guix-patches <at> gnu.org
:
bug#67272
; Package
guix-patches
.
(Mon, 20 Nov 2023 19:39:01 GMT)
Full text and
rfc822 format available.
Message #44 received at 67272 <at> debbugs.gnu.org (full text, mbox):
Am Montag, dem 20.11.2023 um 10:40 +0100 schrieb Rostislav Svoboda:
> Hello
>
> > I disagree. Guix usually sticks to actual releases [...] Note that
> > if the last change was that important for the author, they would
> > have made a release out of it.
>
> Sticking to actual releases makes sense for packages that follow a
> "release-has-a-version" policy, which is common for big & popular
> ones.
>
> But there's a number [see below] of smaller, less popular elisp
> packages with infrequent contributions where the author doesn't
> really bother with a strict "tagged-releases" policy. Sometimes it's
> forgotten over the years, so "rolling-releases" become the norm.
>
> IMO that's the case for our
> https://github.com/thierryvolpiatto/zop-to-char too. Our 00152aa was
> done on May 1, 2018. That's over five years ago. Waiting for 1.2
> doesn't make sense. It's probably not happening anytime soon, not
> even soon-ish, even though the 00152aa seems to be important.
You are right in that it does make sense to not only consider releases,
but Nicolas has already named a reason to do so among several valid
reasons. "It fixes a donation link in the README" is, in my humble
opinion, not that. Now you might want to question whether packaging a
five to seven year old package itself has any technical merit, but I'm
personally quite relaxed w.r.t. that concern.
Cheers
Reply sent
to
Nicolas Goaziou <mail <at> nicolasgoaziou.fr>
:
You have taken responsibility.
(Wed, 19 Jun 2024 07:45:02 GMT)
Full text and
rfc822 format available.
Notification sent
to
Rostislav Svoboda <rostislav.svoboda <at> gmail.com>
:
bug acknowledged by developer.
(Wed, 19 Jun 2024 07:45:02 GMT)
Full text and
rfc822 format available.
Message #49 received at 67272-done <at> debbugs.gnu.org (full text, mbox):
Hello,
Eventually pushed. Thank you!
Regards
--
Nicolas Goaziou
bug archived.
Request was from
Debbugs Internal Request <help-debbugs <at> gnu.org>
to
internal_control <at> debbugs.gnu.org
.
(Wed, 17 Jul 2024 11:24:11 GMT)
Full text and
rfc822 format available.
This bug report was last modified 296 days ago.
Previous Next
GNU bug tracking system
Copyright (C) 1999 Darren O. Benham,
1997,2003 nCipher Corporation Ltd,
1994-97 Ian Jackson.