From: Jan Rehders <jan@sheijk.net>
To: Philip Kaludercic <philipk@posteo.net>
Cc: emacs-devel@gnu.org
Subject: Re: Adding new package hideshowvis to nongnu elpa
Date: Wed, 29 May 2024 13:35:04 +0200 [thread overview]
Message-ID: <4EA8DCA4-0BC4-4E88-B481-DE12E17DDAAE@sheijk.net> (raw)
In-Reply-To: <87cyp55b9l.fsf@posteo.net>
I’ve applied your improvements, thank you!
> Are you sure you don't want the package to be added to GNU ELPA?
If that requires copyright assignment then I’m happy to do that but maybe at a later time. I’m not sure I have the time+energy to do that and check if any contributors submitted more than a few lines right now
> (defun hideshowvis-remove-overlays ()
> "Will remove all overlays added after calling `hideshowvis-symbols'."
> - (when (equal hs-set-up-overlay 'hideshowvis-display-code-line-counts)
> + (when (eq hs-set-up-overlay #'hideshowvis-display-code-line-counts)
> (dolist (ov (overlays-in (point-min) (point-max)))
> - (unless (null (overlay-get ov 'hs))
> + (when (overlay-get ov 'hs) ;why are you returning a `hs' here?
> (overlay-put ov 'after-string nil)))))
Not sure I understand the question - I don’t intend to return anything. I’m using the ‘hs property added by hideshow.el to identify which overlays need to be changed to not break other highlighting packages.
> You can track files to ignore in a .elpaignore file as well. That might
> be better, in case you decide to replace, rename the file or add more.
> I can change that for you, you just have to add the file to the
> repository.
This seems like a good idea, added .elpaignore to the repo
next prev parent reply other threads:[~2024-05-29 11:35 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-28 14:26 Adding new package hideshowvis to nongnu elpa Jan Rehders
2024-05-29 7:26 ` Philip Kaludercic
2024-05-29 11:35 ` Jan Rehders [this message]
2024-06-02 19:45 ` Philip Kaludercic
2024-06-02 20:51 ` Jan Rehders
2024-06-15 13:41 ` Philip Kaludercic
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=4EA8DCA4-0BC4-4E88-B481-DE12E17DDAAE@sheijk.net \
--to=jan@sheijk.net \
--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.