From: Philip Kaludercic <philipk@posteo.net>
To: "Nicolas P. Rougier (inria)" <nicolas.rougier@inria.fr>
Cc: emacs-devel@gnu.org
Subject: Re: ELPA: New package: nano-theme
Date: Wed, 29 Sep 2021 06:24:20 +0000 [thread overview]
Message-ID: <87zgrvucff.fsf@posteo.net> (raw)
In-Reply-To: <m1v92kufqt.fsf@inria.fr> (Nicolas P. Rougier's message of "Wed, 29 Sep 2021 07:07:40 +0200")
"Nicolas P. Rougier (inria)" <nicolas.rougier@inria.fr> writes:
>>>> Furthermore, I wonder why you define the commands nano-light and
>>>> nano-dark, instead of two themes, nano-light and nano-dark (along
>>>> the
>>>> same lines of what modus-themes currently does). You could also
>>>> turn
>>>> nano-setup into a custom theme, so that the user can easily enable
>>>> and
>>>> disable it.
>>>
>>> Maybe I need to read the documentation on what a theme can set. For
>>> example, I set the face for the minibuffer (0 & 1) and echo area (0
>>> &
>>> 1) and I wasn't sure how to specify this in a theme. Same for
>>> underline to be set at descent line, etc.
>>
>> Not directly, but you could define a custom option/minor mode that
>> is
>> activated as part of the theme to change these things too.
>
> But then you need to load the theme and activate the minor mode, do
> you?. Having a (nano-light) command is more direct in my opinion and
> in any case, user is free to only load the theme the regular way.
No, a custom theme can enable a custom option (via
custom-theme-set-variables), and since every minor mode is also a user
option, you can enable a minor mode as part of a theme.
>>>> - Lines 363ff. seem to be indented unconventionally. Maybe add a
>>>> .dir-locals.el to make sure everyone is using the same
>>>> whitespace
>>>> configuration.
>
> I had a mix of space and tabs for unknown reason. Hopefully it has
> been fixed.
>
> Nicolas
>
--
Philip Kaludercic
next prev parent reply other threads:[~2021-09-29 6:24 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-28 13:11 ELPA: New package: nano-theme Nicolas P. Rougier (inria)
2021-09-28 17:47 ` Philip Kaludercic
2021-09-28 17:57 ` Nicolas P. Rougier (inria)
2021-09-28 18:32 ` Stefan Kangas
2021-09-28 18:48 ` Stefan Monnier
2021-09-29 15:20 ` Stefan Kangas
2021-09-29 16:39 ` Stefan Monnier
2021-09-29 5:13 ` Nicolas P. Rougier (inria)
2021-09-29 12:18 ` Stefan Monnier
2021-09-30 7:21 ` Nicolas P. Rougier (inria)
2021-09-28 18:37 ` Philip Kaludercic
2021-09-29 5:07 ` Nicolas P. Rougier (inria)
2021-09-29 6:24 ` Philip Kaludercic [this message]
2021-10-01 9:59 ` Philip Kaludercic
2021-10-01 10:05 ` Nicolas P. Rougier (inria)
2021-10-01 10:15 ` 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=87zgrvucff.fsf@posteo.net \
--to=philipk@posteo.net \
--cc=emacs-devel@gnu.org \
--cc=nicolas.rougier@inria.fr \
/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.