unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Gregor Zattler <grfz@gmx.de>
To: Andrea Corallo <akrl@sdf.org>
Cc: 42265@debbugs.gnu.org
Subject: bug#42265: 28.0.50; different user experience with/out native-comp
Date: Wed, 08 Jul 2020 16:51:25 +0200	[thread overview]
Message-ID: <87fta2njpu.fsf@no.workgroup> (raw)
In-Reply-To: <xjf4kqino2c.fsf@sdf.org>

Hi Andrea,
* Andrea Corallo <akrl@sdf.org> [2020-07-08; 13:17]:
> Gregor Zattler <grfz@gmx.de> writes:
>> I build emacs twice from feature/native-comp as of commit
>> 2593bbee51f4d15d3a4fc1d4e2e3b215222f783a : without and then
>> with --with-nativecomp and NATIVE_FAST_BOOT=1
>>
>> I experience two major differences between these builds:
>>
>> 1. I use emacs-notmuch for mail which shows emails in
>>    searches with tags which are colored, exept when I use
>>    the native-comp version then there are no colors.
>>    Otherwise it works fine.
>>
>> 2. When I open the first org-mode file of the session with
>>    the native-comp build it appears without colors /
>>    different faces on headlines and org-mode links
>>    [[id:foobar][this is a link, only the description should
>>    be seen]] are shown in full as opposed colorized and only
>>    as the descriptive part.  The links work though and if I
>>    use one which opens another org-mode file this is shown
>>    fine.
>>    Whereas if I open the first org-mode file in the build
>>    without --with-nativecomp and NATIVE_FAST_BOOT=1 it shows
>>    up fine.
>>
>> Sorry, this heavily depends on my configuration and
>> therefore I have no receipt with emacs -Q.
>>
>> Please ignore/close if this bug report is too unclear or
>> fixing no priority, I can live very well with a "normal"
>> build of emacs.

> Just a question to understand where to start investigating, have you
> tried compiling without NATIVE_FAST_BOOT and see if it makes a
> difference?

with --with-nativecomp but without NATIVE_FAST_BOOT=1 ?

No.  But I did use it long enough and restartet emacs
several times, so all the eln files could have been
compiled.  Actually I realized the problem over a week ago
and used emacs anyway for most of the time but redid the
test with the two builds yesterday and today.

Is this allready sufficient or should I give it a try
with --with-nativecomp but without NATIVE_FAST_BOOT=1 ?

Ciao,
--
Gregor






  reply	other threads:[~2020-07-08 14:51 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-08 12:21 bug#42265: 28.0.50; different user experience with/out native-comp Gregor Zattler
2020-07-08 13:17 ` Andrea Corallo via Bug reports for GNU Emacs, the Swiss army knife of text editors
2020-07-08 14:51   ` Gregor Zattler [this message]
2020-07-08 15:40     ` Andrea Corallo via Bug reports for GNU Emacs, the Swiss army knife of text editors
2020-07-12  7:31     ` Andrea Corallo via Bug reports for GNU Emacs, the Swiss army knife of text editors
2020-07-15  8:39       ` Gregor Zattler
2020-07-15  9:03         ` Andrea Corallo via Bug reports for GNU Emacs, the Swiss army knife of text editors
2020-07-18 22:59         ` Gregor Zattler
2020-09-08 21:53           ` Gregor Zattler
2020-09-09  7:29             ` Andrea Corallo via Bug reports for GNU Emacs, the Swiss army knife of text editors

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://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87fta2njpu.fsf@no.workgroup \
    --to=grfz@gmx.de \
    --cc=42265@debbugs.gnu.org \
    --cc=akrl@sdf.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.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

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).