How do you see it? modus-operandi is not that different from the current default theme at first sight but it's featureful, very well documented, polished and your maintenance is unsurpassed. And it's because of this last point that I'm not proposing this myself in emacs-devel. I guess maintenance of the default mode could easily take its toll.
That was fast, thanks! It's fixed for me. Are you planning to push it to melpa?
Running modus-themes-20211109.547 on a build from recent emacs master branch the new style *Help*
bindings buffer (C-h b
) looks ill-aligned after enabling modus themes.
For example, before:
After:
This is from a clean run (emacs -q
). modus-operandi was enabled for the second screenshot with default parameters. I tested it with other builtin themes (for example, wombat) but alignment looks ok.
You could add your palettes to base 16 (https://github.com/chriskempson/base16) and leverage the huge amount of templates they already have. Either directly or through your exporter.
I'm using it directly from emacs-28 branch, so it may be that then. Thanks for the detail!
PS: you know, at first your theme looked awful to me and now I cannot help using it, I believe it's the best compliment I can pay because it means you subverted my taste.
Mmmm I now see that there is a much better documented variable:
modus-themes-no-mixed-fonts is a variable defined in ‘../etc/themes/modus-themes.el’.
Its value is nil
Disable inheritance from ‘fixed-pitch’ in some faces.
This is done by default to allow spacing-sensitive constructs,
such as Org tables and code blocks, to remain monospaced when
users opt for something like the command ‘variable-pitch-mode’.
...
Maybe the documentation in https://protesilaos.com/emacs/modus-themes#h:115e6c23-ee35-4a16-8cef-e2fcbb08e28b is outdated?
It persists:
But my answer before was wrong, I was looking at the spec for fixed-pitch, my bad. The inheritance chain is like this:
org-meta-line -> modus-themes-fixed-pitch -> fixed-pitch -> unspecified
The problem is that the family for fixed-pitch is Monospace, not Source Code Pro (which I only set for the default face).
Hi, thanks! I get the same as you. I'm not quite following the explanation. When you say:
it always inherits the
modus-themes-fixed-pitch
face
And the docs says:
When [modus-themes-mixed-fonts is] set to non-nil (t), configure [...] to always inherit from the fixed-pitch face.
What's the point of setting modus-themes-mixed-fonts
to nil then? Using fixed-pitch
instead of modus-themes-fixed-pitch
? But even if it were so it's not what's happening here, because the inherited face is modus-themes-fixed-pitch
.
As things are now, it seems that I would have to set fixed-pitch
or modus-themes-fixed-pitch
to match my default
face.
@cunidev I don't think it's the manual CSS because it's the same story with Adwaita dark.
Ok, I feel a bit stupid now, but I realized that there are more options after "Hide archived projects", it's just that i. they are so perfectly cropped out, ii. the check left to "Hide archived projects" suggests a toggle action and iii. there is no scrollbar until I actually swipe up or down on my touchpad (macOS), what makes it so confusing.
Unchecking "hide archived projects" in my projects list does nothing.
I need some of those projects and I have virtually lost them because I can't remember their names.
I will assume you have an user with archived projects. Just go to your projects and try to list all of them by unchecking the hide archived filter.
Nothing changes, the filter is not removed.
I'm able to access my archived projects.
(For installations with omnibus-gitlab package run and paste the output of: `sudo gitlab-rake gitlab:env:info`) (For installations from source run and paste the output of: `sudo -u git -H bundle exec rake gitlab:env:info RAILS_ENV=production`)
(For installations with omnibus-gitlab package run and paste the output of:
sudo gitlab-rake gitlab:check SANITIZE=true
)(For installations from source run and paste the output of:
sudo -u git -H bundle exec rake gitlab:check RAILS_ENV=production SANITIZE=true
)(we will only investigate if the tests are passing)
Great, thanks for the explanation, I'll be right there in the beta channel for the crazy experience then ;)
Sorry, this is a question, but I don't know if a better place to do it.
The app in Play Store is announced as beta in the title, but there is also the option to join the beta channel, will that do any difference?
When using the Android app any attempt to open a file fails saying that no file was selected. I've tried with a pdf and with a jpg, both from the local filesystem and from Google Drive.
Also, when using "open with" from a file manager, Diurnal++ is not included in the list of available apps.
I now see it's a dup of #3.
Sorry.