From: Fredrik Salomonsson <plattfot@gmail.com>
To: Alexey Abramov <levenson@mmer.org>
Cc: help-guix <help-guix@gnu.org>
Subject: Re: Questions about guix handling emacs packages
Date: Thu, 11 Jun 2020 09:50:33 -0700 [thread overview]
Message-ID: <87imfxo8bq.fsf@gmail.com> (raw)
In-Reply-To: <87k10e6jkp.fsf@mmer.org>
Hi Alexey,
Alexey Abramov <levenson@mmer.org> writes:
> AFAIK emacs-ts is failing on check. There are couple of PRs in the upstream:
>
> https://github.com/alphapapa/ts.el/pull/9
> https://github.com/alphapapa/ts.el/pull/8
Strange, it built fine for me with guix commit:
ba6d3612550f5d978c4b5b1df122444f8fb29377. Maybe those checks aren't fatal?
> Regarding the magit highlighting, emacs 27 has a new face attribute
> :extend. You can read about the issue here https://debbugs.gnu.org/cgi/bugreport.cgi?bug=37774
>
> ,----[ C-h i d m emacs s :extend ]
> | This is one of the few faces that has the ‘:extend t’ attribute by
> | default, which implies that the same face is used to highlight the text
> | and space between end of line and the window border. To highlight only
> | the text you could set this attribute to ‘nil’.
> `----
Nice, did not know about the :extend attribute.
> Magit fix is on the master already https://github.com/magit/magit/commit/891ebdca58ef498ff3b94c8ac2921cc6b72c3d25
>
> In the meantime you can do something like this:
>
> --8<---------------cut here---------------start------------->8---
> (dolist (face '(magit-diff-hunk-heading
> magit-diff-hunk-heading-highlight
> magit-diff-hunk-heading-selection
> magit-diff-hunk-region
> magit-diff-lines-heading
> magit-diff-lines-boundary
> magit-diff-conflict-heading
> magit-diff-added
> magit-diff-removed
> magit-diff-our
> magit-diff-base
> magit-diff-their
> magit-diff-context
> magit-diff-added-highlight
> magit-diff-removed-highlight
> magit-diff-our-highlight
> magit-diff-base-highlight
> magit-diff-their-highlight
> magit-diff-context-highlight
> magit-diff-whitespace-warning
> magit-diffstat-added
> magit-diffstat-removed
> magit-section-heading
> magit-section-heading-selection
> magit-section-highlight
> magit-section-secondary-heading
> magit-diff-file-heading
> magit-diff-file-heading-highlight
> magit-diff-file-heading-selection))
> (set-face-attribute face nil :extend t))
> --8<---------------cut here---------------end--------------->8---
This seems to be fixed in the version of guix I'm using. I don't have
that issue anymore and I'm using emacs 27 and magit from guix.
--
s/Fred[re]+i[ck]+/Fredrik/g
next prev parent reply other threads:[~2020-06-11 16:51 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-23 6:18 Questions about guix handling emacs packages Fredrik Salomonsson
2020-05-25 14:58 ` zimoun
2020-05-25 20:12 ` Fredrik Salomonsson
2020-05-26 8:26 ` zimoun
2020-05-30 2:13 ` Fredrik Salomonsson
2020-06-01 8:15 ` zimoun
2020-06-01 17:12 ` Fredrik Salomonsson
2020-06-02 10:25 ` zimoun
2020-06-02 17:34 ` Fredrik Salomonsson
2020-06-11 9:24 ` Alexey Abramov
2020-06-11 16:50 ` Fredrik Salomonsson [this message]
2020-05-31 2:29 ` Maxim Cournoyer
2020-06-01 3:42 ` Fredrik Salomonsson
2020-06-01 18:37 ` Maxim Cournoyer
2020-06-02 17:37 ` Fredrik Salomonsson
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87imfxo8bq.fsf@gmail.com \
--to=plattfot@gmail.com \
--cc=help-guix@gnu.org \
--cc=levenson@mmer.org \
/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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).