From: Ergus <spacibba@aol.com>
To: Ingo Lohmar <ingo.lohmar@posteo.net>,Eli Zaretskii <eliz@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: :extend t inheritance
Date: Sat, 26 Oct 2019 13:41:33 +0200 [thread overview]
Message-ID: <232434FE-611D-4357-AA7A-95E99CB66E2F@aol.com> (raw)
In-Reply-To: <87pnijkhrm.fsf@kenko.localhost.com>
On October 26, 2019 10:55:41 AM GMT+02:00, Ingo Lohmar <ingo.lohmar@posteo.net> wrote:
>On Sat, Oct 26 2019 03:49 (+0200), Ergus wrote:
>
>> Hi:
>>
>> I just added a branch `fix/inherit_extend_face` that fixes the issue
>> with inheritance of the extend attribute with filter condition.
>>
>> There are two commits because I also detected another issue in gui I
>> didn't see before because I don't use gui normally.
>>
>> Please give it a look and if everything is fine I'll move it to
>master
>> ASAP.
>
>Thanks, I just tried the branch and continued customizing my face
>settings: No everything works as I would expect from inheritance. I
>did
>not see any adverse effects of the changes either, but I only used it
>for about an hour.
>
Could you be more specific please? What is.not working as you expect?
>Looking forward to the changes being merged!
>
>BTW: there seem to be some whitespace-only hunks in the changes..
--
Sent from my Android device with K-9 Mail. Please excuse my brevity.
next prev parent reply other threads:[~2019-10-26 11:41 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-23 20:34 :extend t inheritance Ingo Lohmar
2019-10-24 13:46 ` Eli Zaretskii
2019-10-24 15:38 ` Kévin Le Gouguec
2019-10-24 17:39 ` Ingo Lohmar
2019-10-24 22:22 ` Ergus
2019-10-26 1:49 ` Ergus
2019-10-26 7:28 ` Eli Zaretskii
2019-10-26 19:21 ` Ergus
2019-10-26 19:45 ` Eli Zaretskii
2019-10-26 23:13 ` Ergus
2019-10-27 5:51 ` Eli Zaretskii
2019-10-27 11:01 ` Ergus
2019-10-29 14:27 ` Eli Zaretskii
2019-10-28 21:24 ` Ergus
2019-10-29 3:28 ` Eli Zaretskii
2019-10-26 8:55 ` Ingo Lohmar
2019-10-26 11:41 ` Ergus [this message]
2019-10-26 11:49 ` Ingo Lohmar
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=232434FE-611D-4357-AA7A-95E99CB66E2F@aol.com \
--to=spacibba@aol.com \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=ingo.lohmar@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.