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: Fri, 01 Jul 2016 10:21:09 +0300	[thread overview]
Message-ID: <8360spvn6i.fsf@gnu.org> (raw)
In-Reply-To: <87shvu1ixp.fsf@web.de> (message from Michael Heerdegen on Thu, 30 Jun 2016 23:10:58 +0200)

> From: Michael Heerdegen <michael_heerdegen@web.de>
> Cc: me@wilfred.me.uk,  emacs-devel@gnu.org
> Date: Thu, 30 Jun 2016 23:10:58 +0200
> 
> Eli Zaretskii <eliz@gnu.org> writes:
> 
> > Maybe.  But that doesn't help me debug the issue, does it?  Perhaps
> > someone else can, it's not that hard to dig into these things.
> 
> If you are sure it's a bug (I wasn't)

I don't know yet if it is a bug or not.  Debugging can reveal what it
is.

> I can give it a quick try (I'm on vacation).  How would you do
> proceed?

Insert 'message' in strategic places that print values that are
important for the code flow, and see what is different in the batch
session.  In the interactive session, you can step through the code
with Edebug to compare the findings (you will have to manually load
simple.el into a running session).

Just looking at the code, my first suspect would be line-move: it has
a special code for non-interactive sessions, so maybe the issue hides
there somewhere.  Or maybe it's in line-move-1 or the functions it
calls (like vertical-motion).

Thanks.



  reply	other threads:[~2016-07-01  7:21 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 [this message]
2016-07-05 21:21                 ` Michael Heerdegen
2016-07-05 21:33                   ` Michael Heerdegen
2016-07-06 14:30                     ` Eli Zaretskii
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=8360spvn6i.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.