unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Andrea Crotti <andrea.crotti.0@gmail.com>
To: help-gnu-emacs@gnu.org
Subject: Re: diff-mode
Date: Tue, 14 Dec 2010 16:57:11 +0100	[thread overview]
Message-ID: <m1fwu0z6so.fsf@ip1-201.halifax.rwth-aachen.de> (raw)
In-Reply-To: 332220D46915411C9B8C8CF0DDAF6C40@us.oracle.com

"Drew Adams" <drew.adams@oracle.com> writes:

>> Anyway the error I get when in my configuration I try to kill 
>> the ediff session is
>> 
>> --8<---------------cut here---------------start------------->8---
>> Quit this Ediff session & show containing session group? (y or n) 
>> ediff-cleanup-mess: Attempt to delete minibuffer or sole 
>> ordinary window
>> --8<---------------cut here---------------end--------------->8---
>
> Great.  Now you can report a bug: `M-x report-emacs-bug'.  
>
> First: Load library `ediff-util.el' (the library where `ediff-cleanup-mess' is
> defined.  Be sure to include the ".el" here, so you don't just load the
> byte-compiled file.
>
> Second: `M-x set-variable RET debug-on-error RET t RET', to show a backtrace
> when the error is raised.  Include the backtrace in your bug report.
>
>
> _If_ you want to dig further to help find the problem, you can try to follow
> function `ediff-cleanup-mess' in the debugger:
>
> M-x debug-on-entry RET ediff-cleanup-mess RET
>
> When you try to quit `ediff', the debugger will open when `ediff-cleanup-mess'
> is invoked.  Use `d' to step through the debugger (or `c' to skip through a
> step).  You can add any info you learn this way to your bug report.  (You can
> use command `cancel-debug-on-entry' to cancel `debug-on-entry'.)
>
> Essentially, the problem here is that there is only one window in the Ediff
> control frame, and Emacs tries to delete that lone window, which is a no-no.
> What Emacs should be doing here (probably) is to delete the frame.  Instead, it
> thinks you want to keep the frame and it complains that it cannot delete the
> last window in the frame.  IMO, this is a bug.

Ok thanks a lot I'll do it.
BUT I only experience this with my configuratio as I said.
If I do Emacs -Q I don't have this problem, so I'm not 100% sure that I
should send a bug report until I didn't find the source...




  reply	other threads:[~2010-12-14 15:57 UTC|newest]

Thread overview: 39+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-12-12 11:44 diff-mode Andrea Crotti
2010-12-12 15:09 ` diff-mode Drew Adams
2010-12-12 17:59   ` diff-mode Andrea Crotti
2010-12-12 18:14     ` diff-mode Drew Adams
2010-12-13 23:22       ` diff-mode Andrea Crotti
2010-12-13 23:35         ` diff-mode Drew Adams
2010-12-14 10:04         ` diff-mode Eli Zaretskii
2010-12-14 10:13           ` diff-mode Leo
2010-12-14 11:07             ` diff-mode Eli Zaretskii
2010-12-14 14:40           ` diff-mode Andrea Crotti
2010-12-14 15:22             ` diff-mode Eli Zaretskii
     [not found]           ` <mailman.4.1292337645.794.help-gnu-emacs@gnu.org>
2010-12-14 14:57             ` diff-mode Mario Lassnig
     [not found]       ` <mailman.2.1292282577.11279.help-gnu-emacs@gnu.org>
2010-12-14  8:43         ` diff-mode Elena
2010-12-14 10:11           ` diff-mode Eli Zaretskii
2010-12-14 10:16           ` diff-mode Leo
     [not found]           ` <mailman.1.1292321505.27999.help-gnu-emacs@gnu.org>
2010-12-14 13:40             ` diff-mode Elena
2010-12-14 14:57               ` diff-mode Andrea Crotti
2010-12-14 15:48                 ` diff-mode Drew Adams
2010-12-14 15:57                   ` Andrea Crotti [this message]
2010-12-14 16:06                     ` diff-mode Drew Adams
2010-12-14 15:45               ` diff-mode Richard Riley
     [not found]               ` <mailman.5.1292338693.794.help-gnu-emacs@gnu.org>
2010-12-14 15:35                 ` diff-mode Elena
2010-12-14 16:07                   ` diff-mode Eli Zaretskii
2010-12-14 18:20                     ` diff-mode Andrea Crotti
     [not found]                   ` <mailman.7.1292342885.25302.help-gnu-emacs@gnu.org>
2010-12-14 16:22                     ` diff-mode Elena
2010-12-14 18:51                       ` diff-mode Eli Zaretskii
     [not found]                       ` <mailman.5.1292352715.11323.help-gnu-emacs@gnu.org>
2010-12-14 19:48                         ` diff-mode Elena
2010-12-14 15:46                 ` diff-mode Richard Riley
2010-12-15 14:12               ` diff-mode José A. Romero L.
2010-12-15 15:00                 ` diff-mode Elena
2010-12-15 16:28                   ` diff-mode José A. Romero L.
2010-12-15 16:46                   ` diff-mode José A. Romero L.
2010-12-15 16:50                   ` diff-mode José A. Romero L.
     [not found] <mailman.3.1292154786.23431.help-gnu-emacs@gnu.org>
2010-12-12 12:46 ` diff-mode rusi
2010-12-12 18:02   ` diff-mode Andrea Crotti
     [not found]   ` <mailman.4.1292177110.18751.help-gnu-emacs@gnu.org>
2010-12-13  4:52     ` diff-mode rusi
2010-12-12 18:23 ` diff-mode Elena
2010-12-12 18:26   ` diff-mode Elena
2010-12-15  4:47 ` diff-mode Stefan Monnier

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=m1fwu0z6so.fsf@ip1-201.halifax.rwth-aachen.de \
    --to=andrea.crotti.0@gmail.com \
    --cc=help-gnu-emacs@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.
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).