unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Dmitry Gutov <dgutov@yandex.ru>
To: Eli Zaretskii <eliz@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: [Emacs-diffs] master 108ce84 2/2: xref--next-error-function: Move xref's window point
Date: Sat, 3 Mar 2018 02:49:37 +0200	[thread overview]
Message-ID: <dc0d0cc7-b0ae-f838-290a-133efd353471@yandex.ru> (raw)
In-Reply-To: <83bmg6wmze.fsf@gnu.org>

On 3/2/18 4:50 PM, Eli Zaretskii wrote:
>> Cc: emacs-devel@gnu.org
>> From: Dmitry Gutov <dgutov@yandex.ru>
>> Date: Fri, 2 Mar 2018 16:10:23 +0200
>>
>>>> The reason I figured it's urgent, is step 5 is not necessary with my
>>>> work configuration (not 'emacs -Q'). It's hard for me to tell now which
>>>> package/setting/timer has this effect, but it seems reasonable to
>>>> believe that some other users will see this too. Essentially, the code
>>>> in emacs-26 currently relies on "undefined behavior", in C terms.
>>>
>>> I'm not sure I see where does "undefined behavior" come from.
>>
>> "Behavior I don't understand" might be closer to the truth. :-)
> 
> That's not very inspiring for a release branch...

Well, at least the scope is very limited.

> But okay, please push.

Done, thanks.




      reply	other threads:[~2018-03-03  0:49 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20180228020456.19376.79157@vcs0.savannah.gnu.org>
     [not found] ` <20180228020457.59950207B1@vcs0.savannah.gnu.org>
2018-02-28  2:13   ` [Emacs-diffs] master 108ce84 2/2: xref--next-error-function: Move xref's window point Dmitry Gutov
2018-02-28 15:28     ` Eli Zaretskii
2018-02-28 15:58       ` Dmitry Gutov
2018-03-02 13:39         ` Eli Zaretskii
2018-03-02 14:10           ` Dmitry Gutov
2018-03-02 14:50             ` Eli Zaretskii
2018-03-03  0:49               ` Dmitry Gutov [this message]

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=dc0d0cc7-b0ae-f838-290a-133efd353471@yandex.ru \
    --to=dgutov@yandex.ru \
    --cc=eliz@gnu.org \
    --cc=emacs-devel@gnu.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).