all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Michael Heerdegen <michael_heerdegen@web.de>
Cc: me@wilfred.me.uk, emacs-devel@gnu.org
Subject: Re: Certain numbers of special forms cause changing behaviour on function calls in --batch
Date: Wed, 06 Jul 2016 17:30:02 +0300	[thread overview]
Message-ID: <8337nmon4l.fsf@gnu.org> (raw)
In-Reply-To: <871t37n51y.fsf@web.de> (message from Michael Heerdegen on Tue, 05 Jul 2016 23:33:29 +0200)

> From: Michael Heerdegen <michael_heerdegen@web.de>
> Cc: me@wilfred.me.uk,  emacs-devel@gnu.org
> Date: Tue, 05 Jul 2016 23:33:29 +0200
> 
> Hmm, now I changed simple.el like this:
> 
> *** /tmp/ediff230416Vp	2016-07-05 23:29:32.557789593 +0200
> --- /home/micha/software/emacs/lisp/simple.el	2016-07-05 23:27:12.017360250 +0200
> ***************
> *** 6341,6346 ****
> --- 6341,6347 ----
>                                         (point) 'invisible)))
>   			(backward-char 1)))
>   		 (point)))))
> +         (message "%s" newpos)
>   	(goto-char newpos)
>   	(if (and (> (point) newpos)
>   		 (eq (preceding-char) ?\n))
> 
> and recompiled it.  After that, the issue is not reproducible anymore at
> all; neither with the uncompiled nor with compiled "simple" library.

Did the experiments with the compiled simple.elc load it into a
running session, or did you re-dump Emacs after byte-compiling
simple.el?

> Seems we won't find out anything useful by debugging on the Lisp level.

What other practical alternatives are there?



  reply	other threads:[~2016-07-06 14:30 UTC|newest]

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-06-26 16:39 Certain numbers of special forms cause changing behaviour on function calls in --batch Wilfred Hughes
2016-06-28 21:12 ` Michael Heerdegen
2016-06-29 16:23   ` Eli Zaretskii
2016-06-29 20:39     ` Michael Heerdegen
2016-06-30  2:38       ` Eli Zaretskii
2016-06-30 12:34         ` Michael Heerdegen
2016-06-30 15:19           ` Eli Zaretskii
2016-06-30 21:10             ` Michael Heerdegen
2016-07-01  7:21               ` Eli Zaretskii
2016-07-05 21:21                 ` Michael Heerdegen
2016-07-05 21:33                   ` Michael Heerdegen
2016-07-06 14:30                     ` Eli Zaretskii [this message]
2016-07-06 14:47                       ` Michael Heerdegen
2016-07-06 15:04                         ` Eli Zaretskii
2016-07-10 10:34                           ` Yasushi SHOJI
2016-07-10 11:13                             ` Yasushi SHOJI
2016-07-10 11:33                               ` Noam Postavsky
2016-07-10 14:53                                 ` Eli Zaretskii
2016-07-10 16:23                                   ` Noam Postavsky
2016-07-10 16:45                                     ` Eli Zaretskii
2016-07-10 17:03                                       ` Noam Postavsky
2016-07-10 17:29                                         ` Eli Zaretskii
2016-07-10 17:10                                       ` Andreas Schwab
2016-07-10 17:37                                         ` Eli Zaretskii
2016-07-10 18:40                                           ` Paul Eggert
2016-07-10 19:09                                             ` Eli Zaretskii
2016-07-10 17:37                                         ` Andreas Schwab
2016-07-10 18:02                                           ` Eli Zaretskii
     [not found]                                           ` <<83inwde5gv.fsf@gnu.org>
2016-07-10 18:20                                             ` Drew Adams
2016-07-10 21:44                                           ` Clément Pit--Claudel
2016-07-06 14:28                   ` Eli Zaretskii
2016-06-30  5:58   ` Andreas Röhler
2016-06-30 15:13     ` Eli Zaretskii
2016-06-30 17:20       ` Andreas Röhler
2016-06-30 17:40         ` Eli Zaretskii
2016-06-30 21:22       ` Michael Heerdegen
2016-07-01  7:13         ` Eli Zaretskii

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=8337nmon4l.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=me@wilfred.me.uk \
    --cc=michael_heerdegen@web.de \
    /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.