unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: "Óscar Fuentes" <ofv@wanadoo.es>
Cc: 21054@debbugs.gnu.org
Subject: bug#21054: Reopen
Date: Wed, 18 Nov 2015 19:27:15 +0200	[thread overview]
Message-ID: <83twoj9q18.fsf@gnu.org> (raw)
In-Reply-To: <87wptg7y9c.fsf@wanadoo.es>

> From: Óscar Fuentes <ofv@wanadoo.es>
> Date: Wed, 18 Nov 2015 05:00:15 +0100
> 
> After a proper build (full rebuild from a pristine checkout; something
> is wrong with the Emacs build system) the problem is still there.

The changeset you identified as the one to blame is huge, even if we
look only at changes in ses.el.  Would it be possible for you to try
to locate the code that specifically caused this misbehavior?  Or
maybe you already know that?

Armed with that knowledge, we could see how to fix this annoying
problem, which IMO should block Emacs 25.1 release, unless we fix it
soon.

Thanks.





  reply	other threads:[~2015-11-18 17:27 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-14 10:39 bug#21054: 25.0.50; Can't edit SES documents: Not at cell Óscar Fuentes
     [not found] ` <handler.21054.B.14368703993315.ack@debbugs.gnu.org>
2015-07-14 23:10   ` bug#21054: Acknowledgement (25.0.50; Can't edit SES documents: Not at cell) Óscar Fuentes
2015-08-23 13:54     ` bug#21054: 25.0.50; Can't edit SES documents: Not at cell Óscar Fuentes
2015-08-23 22:37       ` Stefan Monnier
2015-11-18  2:23 ` bug#21054: Fixed Óscar Fuentes
2015-11-18  4:00 ` bug#21054: Reopen Óscar Fuentes
2015-11-18 17:27   ` Eli Zaretskii [this message]
2015-11-18 19:03     ` bug#21054: 25.0.50; Can't edit SES documents: Not at cell Óscar Fuentes
2015-11-18 19:46       ` Óscar Fuentes
2015-11-19 17:11     ` bug#21054: Reopen Stephen Leake
2015-11-19 17:17       ` Stephen Leake
2015-11-19 17:37         ` Stephen Leake
2015-11-20 12:55           ` Óscar Fuentes
2016-01-01  5:42 ` bug#21054: 25.0.50; Can't edit SES documents: Not at cell Óscar Fuentes
2016-01-02 16:07 ` Vincent Belaïche

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=83twoj9q18.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=21054@debbugs.gnu.org \
    --cc=ofv@wanadoo.es \
    /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).