bug in emacs-ui ?

bug in emacs-ui ?

[Sebastien Binet]

[-- Attachment #1: Type: text/plain, Size: 685 bytes --]

hi there,

recently, using the head of notmuch-git:

 git://notmuchmail.org/git/notmuch

when a mail ends with an url and is recognized as a signature:

      ==============================================================================

      This item URL is:
        <http://savannah.cern.ch/bugs/?83337>

      [ 4-line signature. Click/Enter to hide. ]
      _______________________________________________
      Message sent via/by LCG Savannah
      http://savannah.cern.ch/

I can't hit [space] to go to the next thread and I get the following
error:
 End of buffer

this does not show up when using the 'release-candidate/0.6' branch of:
 git://finestructure.net/notmuch

-s

[-- Attachment #2: Type: application/pgp-signature, Size: 197 bytes --]

Re: bug in emacs-ui ?

[Jameson Graef Rollins]

[-- Attachment #1: Type: text/plain, Size: 1794 bytes --]

On Mon, 20 Jun 2011 09:15:06 +0200, Sebastien Binet <seb.binet@gmail.com> wrote:
> recently, using the head of notmuch-git:
> 
>  git://notmuchmail.org/git/notmuch
> 
> when a mail ends with an url and is recognized as a signature:
...
> I can't hit [space] to go to the next thread and I get the following
> error:
>  End of buffer

Hey, Sebastien.  I'm guessing that it is probably the *next* message in
the thread that is the problem, not the end of the one that you're
seeing.  If you can determine the message id's of this message and the
next one in the thread it will probably help with debugging.

If you haven't yet, it usually helps in debugging to view the messages
in the terminal?  You can copy the thread-id into the clipboard by
hitting "c i" when the cursor is over this thread in the notmuch search
buffer, and then you can view the thread on the command line with:

  notmuch show thread:<thread-id>

It might be hard to see if there are any problems in the output, but you
can at least see gmime is throwing an error by redirecting stdout to
/dev/null:

  notmuch show thread:<thread-id> >/dev/null

You can try determining the message-ids with something like:

  notmuch show thread:<thread-id> | grep id

You can then view the raw messages with:

  notmuch show --format=raw id:<message-id>

If you feel comfortable doing so, it might help to forward the suspect
message to the list.

> this does not show up when using the 'release-candidate/0.6' branch of:
>  git://finestructure.net/notmuch

The release-candidate/0.6 is a bit out-of-date at the moment, as most of
it's features have been incorporate into notmuch/master, and I doubt
that the ones that haven't would be related to the issue you're seeing.

hth.

jamie.

[-- Attachment #2: Type: application/pgp-signature, Size: 835 bytes --]

Re: bug in emacs-ui ?

[Sebastien Binet]

[-- Attachment #1: Type: text/plain, Size: 2719 bytes --]

Jamie,

On Mon, 20 Jun 2011 08:16:00 -0700, Jameson Graef Rollins <jrollins@finestructure.net> wrote:
Non-text part: multipart/signed
> On Mon, 20 Jun 2011 09:15:06 +0200, Sebastien Binet <seb.binet@gmail.com> wrote:
> > recently, using the head of notmuch-git:
> > 
> >  git://notmuchmail.org/git/notmuch
> > 
> > when a mail ends with an url and is recognized as a signature:
> ...
> > I can't hit [space] to go to the next thread and I get the following
> > error:
> >  End of buffer
> 
> Hey, Sebastien.  I'm guessing that it is probably the *next* message in
> the thread that is the problem, not the end of the one that you're
> seeing.
I (naively) don't think so:
I don't get the error (which looks like that in the *Messages* buffer:
notmuch-show-advance-and-archive: End of buffer
)
if I unravel the signature:
      [ 4-line signature. Click/Enter to hide. ]
      _______________________________________________
      Message sent via/by LCG Savannah
      http://savannah.cern.ch/

=> all is fine.

it is only when the signature is lumped like below, that I get the error:
      [ 4-line signature. Click/Enter to show. ]

also, it's only happening to the last message of a thread.

>  If you can determine the message id's of this message and the
> next one in the thread it will probably help with debugging.
> 
> If you haven't yet, it usually helps in debugging to view the messages
> in the terminal?  You can copy the thread-id into the clipboard by
> hitting "c i" when the cursor is over this thread in the notmuch search
> buffer, and then you can view the thread on the command line with:
> 
>   notmuch show thread:<thread-id>
> 
> It might be hard to see if there are any problems in the output, but you
> can at least see gmime is throwing an error by redirecting stdout to
> /dev/null:
> 
>   notmuch show thread:<thread-id> >/dev/null
> 
> You can try determining the message-ids with something like:
> 
>   notmuch show thread:<thread-id> | grep id
> 
> You can then view the raw messages with:
> 
>   notmuch show --format=raw id:<message-id>
> 
> If you feel comfortable doing so, it might help to forward the suspect
> message to the list.

I tried all the above, to no avail (ie: nothing on stderr.)

> 
> > this does not show up when using the 'release-candidate/0.6' branch of:
> >  git://finestructure.net/notmuch
> 
> The release-candidate/0.6 is a bit out-of-date at the moment, as most of
> it's features have been incorporate into notmuch/master, and I doubt
> that the ones that haven't would be related to the issue you're
> seeing.

hum... I could try to bisect (but I've never done that before!)

-s

[-- Attachment #2: Type: application/pgp-signature, Size: 197 bytes --]

Re: bug in emacs-ui ?

[Jameson Graef Rollins]

[-- Attachment #1: Type: text/plain, Size: 635 bytes --]

On Mon, 20 Jun 2011 17:52:03 +0200, Sebastien Binet <seb.binet@gmail.com> wrote:
> it is only when the signature is lumped like below, that I get the error:
>       [ 4-line signature. Click/Enter to show. ]
> 
> also, it's only happening to the last message of a thread.

Ah, ok.  Have you tried looking at the raw message?  Are there any
strange characters or content after the signatures?

> > If you feel comfortable doing so, it might help to forward the suspect
> > message to the list.
> 
> I tried all the above, to no avail (ie: nothing on stderr.)

You didn't try forwarding the email to the list ;)

jamie.

[-- Attachment #2: Type: application/pgp-signature, Size: 835 bytes --]

Re: bug in emacs-ui ?

[Sebastien Binet]

[-- Attachment #1.1: Type: text/plain, Size: 847 bytes --]

On Mon, 20 Jun 2011 09:17:32 -0700, Jameson Graef Rollins <jrollins@finestructure.net> wrote:
Non-text part: multipart/signed
> On Mon, 20 Jun 2011 17:52:03 +0200, Sebastien Binet <seb.binet@gmail.com> wrote:
> > it is only when the signature is lumped like below, that I get the error:
> >       [ 4-line signature. Click/Enter to show. ]
> > 
> > also, it's only happening to the last message of a thread.
> 
> Ah, ok.  Have you tried looking at the raw message?  Are there any
> strange characters or content after the signatures?
nope.
at least none that I can see.

> 
> > > If you feel comfortable doing so, it might help to forward the suspect
> > > message to the list.
> > 
> > I tried all the above, to no avail (ie: nothing on stderr.)
> 
> You didn't try forwarding the email to the list ;)
ah! that easy, heh ?


[-- Attachment #1.2: 1300323326_0.6276.farnsworth,U=250482,FMD5=af1cd994dfcb9286c394d142687ff5a0:2,S --]
[-- Type: application/octet-stream, Size: 5944 bytes --]

Delivered-To: seb.binet@gmail.com
Received: by 10.229.94.140 with SMTP id z12cs72439qcm;
        Wed, 16 Mar 2011 17:52:50 -0700 (PDT)
Received: by 10.216.7.8 with SMTP id 8mr157459weo.30.1300323169395;
        Wed, 16 Mar 2011 17:52:49 -0700 (PDT)
Return-Path: <sebastien.binet@cern.ch>
Received: from CERNMX32.cern.ch (cernmx32.cern.ch [137.138.144.178])
        by mx.google.com with ESMTPS id o51si3199595wee.136.2011.03.16.17.52.48
        (version=TLSv1/SSLv3 cipher=OTHER);
        Wed, 16 Mar 2011 17:52:49 -0700 (PDT)
Received-SPF: pass (google.com: domain of sebastien.binet@cern.ch designates 137.138.144.178 as permitted sender) client-ip=137.138.144.178;
Authentication-Results: mx.google.com; spf=pass (google.com: domain of sebastien.binet@cern.ch designates 137.138.144.178 as permitted sender) smtp.mail=sebastien.binet@cern.ch; dkim=neutral (body hash did not verify) header.i=jsquyres@cisco.com
Received: from CERNFE23.cern.ch (137.138.144.152) by cernmxgwlb2.cern.ch
 (137.138.144.178) with Microsoft SMTP Server (TLS) id 14.1.270.1; Thu, 17 Mar
 2011 01:52:48 +0100
Resent-From: <sebastien.binet@cern.ch>
Received: from CERNMX30.cern.ch (137.138.144.177) by CERNFE23.cern.ch
 (137.138.144.152) with Microsoft SMTP Server (TLS) id 14.1.270.2; Thu, 17 Mar
 2011 01:52:48 +0100
Received: from milliways.osl.iu.edu (129.79.245.239) by cernmxgwlb2.cern.ch
 (137.138.144.183) with Microsoft SMTP Server (TLS) id 14.1.270.1; Thu, 17 Mar
 2011 01:52:47 +0100
Received: from milliways.osl.iu.edu (localhost [127.0.0.1])	by
 milliways.osl.iu.edu (8.13.1/8.13.1/IUCS_2.93) with ESMTP id p2H0mcw6028453;
	Wed, 16 Mar 2011 20:52:33 -0400
Received: from sj-iport-1.cisco.com (sj-iport-1.cisco.com [171.71.176.70])	by
 milliways.osl.iu.edu (8.13.1/8.13.1/IUCS_2.93) with ESMTP id	p2H0mXqc028449
	for <announce@open-mpi.org>; Wed, 16 Mar 2011 20:48:37 -0400
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple;
	d=cisco.com; i=jsquyres@cisco.com; l=1052; q=dns/txt;
	s=iport; t=1300322917; x=1301532517;
	h=from:content-transfer-encoding:subject:date:message-id:
	to:mime-version;
	bh=v/0wsVXEpLp/nW8MnJ3nkvg6NNSU/ob4tfq7/HS8kjs=;
	b=dx+oaDxQh6Ti00xLYBNiJ8M1aHcYabjOnSAyHpZNIMkfWFvosWPJzm23
	7ENYPXcp4qHi93mP4NQt4AgQBsHj0L0J52hkzq5zyR5MFT74F2h7kixY9
	2WJASCJNk2jHqaUruQgKzwKKzS4FrfZmI+inyO8xzRyEc87totCORil1e w=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AvsEANL3gE2tJXG+/2dsb2JhbAClUHemG5xehWMEjF4
X-IronPort-AV: E=Sophos;i="4.63,196,1299456000"; d="scan'208";a="415197591"
Received: from rcdn-core2-3.cisco.com ([173.37.113.190])	by
 sj-iport-1.cisco.com with ESMTP; 17 Mar 2011 00:48:18 +0000
Received: from rtp-jsquyres-8713.cisco.com (rtp-jsquyres-8713.cisco.com
	[10.116.19.196])	by rcdn-core2-3.cisco.com (8.14.3/8.14.3) with ESMTP id
 p2H0mIRK006019	for <announce@open-mpi.org>; Thu, 17 Mar 2011 00:48:18 GMT
From: Jeff Squyres <jsquyres@cisco.com>
Date: Wed, 16 Mar 2011 20:48:18 -0400
Message-ID: <849C2ABC-7647-4BDD-9E71-F1DA405C6ECA@cisco.com>
To: Open MPI Announcements <announce@open-mpi.org>
MIME-Version: 1.0 (Apple Message framework v1082)
X-Mailer: Apple Mail (2.1082)
X-PMX-Version: 5.5.9.388399, Antispam-Engine: 2.7.2.376379,
	Antispam-Data: 2011.3.17.2718
X-PerlMx-Spam: Gauge=IIIIIIII, Probability=8%, Report='
	SUPERLONG_LINE 0.05, BODYTEXTP_SIZE_3000_LESS 0, BODY_SIZE_1000_1099 0,
	BODY_SIZE_2000_LESS 0, BODY_SIZE_5000_LESS 0,
	BODY_SIZE_7000_LESS 0, DATE_TZ_NA 0, __CP_URI_IN_BODY 0, __CT 0,
	__CTE 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __HAS_X_MAILER 0,
	__MIME_TEXT_ONLY 0, __MIME_VERSION 0, __MIME_VERSION_APPLEMAIL 0,
	__MSGID_APPLEMAIL 0, __SANE_MSGID 0, __TO_MALFORMED_2 0,
	__URI_NS , __USER_AGENT_APPLEMAIL 0, __X_MAILER_APPLEMAIL 0'
X-MIME-Autoconverted: from quoted-printable to 8bit by milliways.osl.iu.edu id
	p2H0mXqc028449
Subject: [Open MPI Announce] Open MPI v1.5.3 released
X-BeenThere: announce@open-mpi.org
X-Mailman-Version: 2.1.11rc1
Precedence: list
Reply-To: <users@open-mpi.org>
List-Id: Open MPI announcements <announce.open-mpi.org>
List-Unsubscribe: <http://www.open-mpi.org/mailman/options.cgi/announce>,
	<mailto:announce-request@open-mpi.org?subject=unsubscribe>
List-Archive: <http://www.open-mpi.org/MailArchives/announce>
List-Post: <mailto:announce@open-mpi.org>
List-Help: <mailto:announce-request@open-mpi.org?subject=help>
List-Subscribe: <http://www.open-mpi.org/mailman/listinfo.cgi/announce>,
	<mailto:announce-request@open-mpi.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: <announce-bounces@open-mpi.org>
Errors-To: announce-bounces@open-mpi.org
Return-Path: announce-bounces@open-mpi.org
Received-SPF: None (CERNMX30.cern.ch: announce-bounces@open-mpi.org does not
 designate permitted sender hosts)
Keywords: CERN SpamKiller Note: -5

The Open MPI Team, representing a consortium of research, academic, and industry partners, is pleased to announce the release of Open MPI version 1.5.3.  This release adds a feature that was accidentally left out of v1.5.2.

*** Note that the "v1.5.x" series is the "feature development" series for Open MPI.  We consider it fairly stable, but it has not been as time-tested as the mature v1.4.x series.  Production sites may wish to stay with v1.4.x until the v1.5 series transitions to its "mature" counterpart (i.e., the v1.6 series). 

Version 1.5.3 can be downloaded from the main Open MPI web site or any of its mirrors (mirrors will be updating shortly). 

Here is a list of changes in v1.5.3 as compared to v1.5.2: 

1.5.3
-----

- Add missing "affinity" MPI extension (i.e., the OMPI_Affinity_str()
  API) that was accidentally left out of the 1.5.2 release.

-- 
Jeff Squyres
jsquyres@cisco.com
For corporate legal information go to:
http://www.cisco.com/web/about/doing_business/legal/cri/


_______________________________________________
announce mailing list
announce@open-mpi.org
http://www.open-mpi.org/mailman/listinfo.cgi/announce

[-- Attachment #1.3: Type: text/plain, Size: 45 bytes --]


here is also the json dump of that message:

[-- Attachment #1.4: tmp.openmpi.message.json --]
[-- Type: application/octet-stream, Size: 1681 bytes --]

\fmessage{ id:849C2ABC-7647-4BDD-9E71-F1DA405C6ECA@cisco.com depth:0 match:1 filename:/home/binet/mail-notmuch/gmail/inbox/cur/1300323326_0.6276.farnsworth,U=250482,FMD5=af1cd994dfcb9286c394d142687ff5a0:2,S
\fheader{
Jeff Squyres <jsquyres@cisco.com> (March 17) (sci-mpi)
Subject: [Open MPI Announce] Open MPI v1.5.3 released
From: Jeff Squyres <jsquyres@cisco.com>
To: Open MPI Announcements <announce@open-mpi.org>
Date: Wed, 16 Mar 2011 20:48:18 -0400
\fheader}
\fbody{
\fpart{ ID: 1, Content-type: text/plain
The Open MPI Team, representing a consortium of research, academic, and industry partners, is pleased to announce the release of Open MPI version 1.5.3.  This release adds a feature that was accidentally left out of v1.5.2.

*** Note that the "v1.5.x" series is the "feature development" series for Open MPI.  We consider it fairly stable, but it has not been as time-tested as the mature v1.4.x series.  Production sites may wish to stay with v1.4.x until the v1.5 series transitions to its "mature" counterpart (i.e., the v1.6 series). 

Version 1.5.3 can be downloaded from the main Open MPI web site or any of its mirrors (mirrors will be updating shortly). 

Here is a list of changes in v1.5.3 as compared to v1.5.2: 

1.5.3
-----

- Add missing "affinity" MPI extension (i.e., the OMPI_Affinity_str()
  API) that was accidentally left out of the 1.5.2 release.

-- 
Jeff Squyres
jsquyres@cisco.com
For corporate legal information go to:
http://www.cisco.com/web/about/doing_business/legal/cri/


_______________________________________________
announce mailing list
announce@open-mpi.org
http://www.open-mpi.org/mailman/listinfo.cgi/announce
\fpart}
\fbody}
\fmessage}

[-- Attachment #1.5: Type: text/plain, Size: 9 bytes --]


hth,
-s

[-- Attachment #2: Type: application/pgp-signature, Size: 197 bytes --]

Re: bug in emacs-ui ?

[Jameson Graef Rollins]

[-- Attachment #1: Type: text/plain, Size: 960 bytes --]

On Mon, 20 Jun 2011 18:43:01 +0200, Sebastien Binet <seb.binet@gmail.com> wrote:
> > You didn't try forwarding the email to the list ;)
> ah! that easy, heh ?
>
> Attachment: 1300323326_0.6276.farnsworth,U=250482,FMD5=af1cd994dfcb9286c394d142687ff5a0:2,S (application/octet-stream)

Are you sure this is the right message?  This message doesn't include
any signature section that looks like the one that you posted before.
The one you posted in your previous message was:

_______________________________________________
Message sent via/by LCG Savannah
http://savannah.cern.ch/

This one is:

_______________________________________________
announce mailing list
announce@open-mpi.org
http://www.open-mpi.org/mailman/listinfo.cgi/announce

Also (unrelated) I notice that the above attached message is not
content-type "message/rfc822".  Specifying the right content type helps 
receivers handle the messages a little better.

jamie.

[-- Attachment #2: Type: application/pgp-signature, Size: 835 bytes --]

Re: bug in emacs-ui ?

[Sebastien Binet]

[-- Attachment #1: Type: text/plain, Size: 1490 bytes --]

On Mon, 20 Jun 2011 11:18:11 -0700, Jameson Graef Rollins <jrollins@finestructure.net> wrote:
Non-text part: multipart/signed
> On Mon, 20 Jun 2011 18:43:01 +0200, Sebastien Binet <seb.binet@gmail.com> wrote:
> > > You didn't try forwarding the email to the list ;)
> > ah! that easy, heh ?
> >
> > Attachment: 1300323326_0.6276.farnsworth,U=250482,FMD5=af1cd994dfcb9286c394d142687ff5a0:2,S (application/octet-stream)
> 
> Are you sure this is the right message?  This message doesn't include
> any signature section that looks like the one that you posted before.
> The one you posted in your previous message was:
> 
> _______________________________________________
> Message sent via/by LCG Savannah
> http://savannah.cern.ch/
> 
> This one is:
> 
> _______________________________________________
> announce mailing list
> announce@open-mpi.org
> http://www.open-mpi.org/mailman/listinfo.cgi/announce

it is indeed another message but one which presents the same problem
(the other one was from a semi-private mailing list...)

> 
> Also (unrelated) I notice that the above attached message is not
> content-type "message/rfc822".  Specifying the right content type helps 
> receivers handle the messages a little better.
duly noted.

-s
-- 
#########################################
# Dr. Sebastien Binet
# Laboratoire de l'Accelerateur Lineaire
# Universite Paris-Sud XI
# Batiment 200
# 91898 Orsay
#########################################

[-- Attachment #2: Type: application/pgp-signature, Size: 197 bytes --]

Re: bug in emacs-ui ?

[Pieter Praet]

On Mon, 20 Jun 2011 21:06:09 +0200, Sebastien Binet <seb.binet@gmail.com> wrote:
Non-text part: multipart/mixed
Non-text part: multipart/signed
> On Mon, 20 Jun 2011 11:18:11 -0700, Jameson Graef Rollins <jrollins@finestructure.net> wrote:
> Non-text part: multipart/signed
> > On Mon, 20 Jun 2011 18:43:01 +0200, Sebastien Binet <seb.binet@gmail.com> wrote:
> > > > You didn't try forwarding the email to the list ;)
> > > ah! that easy, heh ?
> > >
> > > Attachment: 1300323326_0.6276.farnsworth,U=250482,FMD5=af1cd994dfcb9286c394d142687ff5a0:2,S (application/octet-stream)
> > 
> > Are you sure this is the right message?  This message doesn't include
> > any signature section that looks like the one that you posted before.
> > The one you posted in your previous message was:
> > 
> > _______________________________________________
> > Message sent via/by LCG Savannah
> > http://savannah.cern.ch/
> > 
> > This one is:
> > 
> > _______________________________________________
> > announce mailing list
> > announce@open-mpi.org
> > http://www.open-mpi.org/mailman/listinfo.cgi/announce
> 
> it is indeed another message but one which presents the same problem
> (the other one was from a semi-private mailing list...)

Appears to occur with *every* message which
- has a collapsed signature
- is last in a thread

I'm awake longer than I care to admit, so don't take my word for it,
but notmuch-show.el:1128 (on master, 12d6f90e) should be where it's at.

Most probably an unfortunate side-effect of Dmitry's (excellent) recent
visibility patches.

> > 
> > Also (unrelated) I notice that the above attached message is not
> > content-type "message/rfc822".  Specifying the right content type helps 
> > receivers handle the messages a little better.
> duly noted.
> 
> -s
> -- 
> #########################################
> # Dr. Sebastien Binet
> # Laboratoire de l'Accelerateur Lineaire
> # Universite Paris-Sud XI
> # Batiment 200
> # 91898 Orsay
> #########################################
Non-text part: application/pgp-signature
> _______________________________________________
> notmuch mailing list
> notmuch@notmuchmail.org
> http://notmuchmail.org/mailman/listinfo/notmuch

Peace

-- 
Pieter

Re: bug in emacs-ui ?

[Jameson Graef Rollins]

[-- Attachment #1: Type: text/plain, Size: 748 bytes --]

On Mon, 20 Jun 2011 18:43:01 +0200, Sebastien Binet <seb.binet@gmail.com> wrote:
> > You didn't try forwarding the email to the list ;)
> ah! that easy, heh ?
> 
Attachment: 1300323326_0.6276.farnsworth,U=250482,FMD5=af1cd994dfcb9286c394d142687ff5a0:2,S (application/octet-stream)

Hi, Sebastien.  I don't seem to have any problems viewing this message
with notmuch emacs.  Is it possible that the notmuch emacs code you're
running is out-of-sync with your notmuch binary?  I think that's a
common source of problems like this.  Make sure that you're pointed to
the version of the notmuch emacs libraries that corresponds to your
notmuch binary, and that you've restarted your emacs session.  Hopefully
that will fix things.

jamie.

[-- Attachment #2: Type: application/pgp-signature, Size: 835 bytes --]

Re: bug in emacs-ui ?

[Pieter Praet]

On Mon, 20 Jun 2011 12:53:37 -0700, Jameson Graef Rollins <jrollins@finestructure.net> wrote:
Non-text part: multipart/mixed
Non-text part: multipart/signed
> On Mon, 20 Jun 2011 18:43:01 +0200, Sebastien Binet <seb.binet@gmail.com> wrote:
> > > You didn't try forwarding the email to the list ;)
> > ah! that easy, heh ?
> > 
> Attachment: 1300323326_0.6276.farnsworth,U=250482,FMD5=af1cd994dfcb9286c394d142687ff5a0:2,S (application/octet-stream)
> 
> Hi, Sebastien.  I don't seem to have any problems viewing this message
> with notmuch emacs.  Is it possible that the notmuch emacs code you're
> running is out-of-sync with your notmuch binary?  [...]

+1. Stale notmuch binary was indeed the culprit.

> [..] I think that's a
> common source of problems like this.  Make sure that you're pointed to
> the version of the notmuch emacs libraries that corresponds to your
> notmuch binary, and that you've restarted your emacs session.  Hopefully
> that will fix things.
> 
> jamie.
Non-text part: application/pgp-signature
> _______________________________________________
> notmuch mailing list
> notmuch@notmuchmail.org
> http://notmuchmail.org/mailman/listinfo/notmuch

Peace

-- 
Pieter

Re: bug in emacs-ui ?

[Sebastien Binet]

[-- Attachment #1: Type: text/plain, Size: 3879 bytes --]

hi,

On Mon, Jun 20, 2011 at 9:53 PM, Jameson Graef Rollins <
jrollins@finestructure.net> wrote:

> On Mon, 20 Jun 2011 18:43:01 +0200, Sebastien Binet <seb.binet@gmail.com>
> wrote:
> > > You didn't try forwarding the email to the list ;)
> > ah! that easy, heh ?
> >
> Attachment:
> 1300323326_0.6276.farnsworth,U=250482,FMD5=af1cd994dfcb9286c394d142687ff5a0:2,S
> (application/octet-stream)
>
> Hi, Sebastien.  I don't seem to have any problems viewing this message
> with notmuch emacs.  Is it possible that the notmuch emacs code you're
> running is out-of-sync with your notmuch binary?  I think that's a
> common source of problems like this.  Make sure that you're pointed to
> the version of the notmuch emacs libraries that corresponds to your
> notmuch binary, and that you've restarted your emacs session.  Hopefully
> that will fix things.
>

no joy:
$ `which notmuch` --version
notmuch 0.5-238-gc39b492

$ pacman -Ql notmuch-git
notmuch-git /etc/
notmuch-git /etc/bash_completion.d/
notmuch-git /etc/bash_completion.d/notmuch
notmuch-git /usr/
notmuch-git /usr/bin/
notmuch-git /usr/bin/notmuch
notmuch-git /usr/include/
notmuch-git /usr/include/notmuch.h
notmuch-git /usr/lib/
notmuch-git /usr/lib/libnotmuch.so
notmuch-git /usr/lib/libnotmuch.so.1
notmuch-git /usr/lib/libnotmuch.so.1.3.0
notmuch-git /usr/lib/python2.7/
 [other python files elided]
notmuch-git /usr/share/
notmuch-git /usr/share/emacs/
notmuch-git /usr/share/emacs/site-lisp/
notmuch-git /usr/share/emacs/site-lisp/coolj.el
notmuch-git /usr/share/emacs/site-lisp/coolj.elc
notmuch-git /usr/share/emacs/site-lisp/notmuch-address.el
notmuch-git /usr/share/emacs/site-lisp/notmuch-address.elc
notmuch-git /usr/share/emacs/site-lisp/notmuch-crypto.el
notmuch-git /usr/share/emacs/site-lisp/notmuch-crypto.elc
notmuch-git /usr/share/emacs/site-lisp/notmuch-hello.el
notmuch-git /usr/share/emacs/site-lisp/notmuch-hello.elc
notmuch-git /usr/share/emacs/site-lisp/notmuch-lib.el
notmuch-git /usr/share/emacs/site-lisp/notmuch-lib.elc
notmuch-git /usr/share/emacs/site-lisp/notmuch-logo.png
notmuch-git /usr/share/emacs/site-lisp/notmuch-maildir-fcc.el
notmuch-git /usr/share/emacs/site-lisp/notmuch-maildir-fcc.elc
notmuch-git /usr/share/emacs/site-lisp/notmuch-message.el
notmuch-git /usr/share/emacs/site-lisp/notmuch-message.elc
notmuch-git /usr/share/emacs/site-lisp/notmuch-mua.el
notmuch-git /usr/share/emacs/site-lisp/notmuch-mua.elc
notmuch-git /usr/share/emacs/site-lisp/notmuch-query.el
notmuch-git /usr/share/emacs/site-lisp/notmuch-query.elc
notmuch-git /usr/share/emacs/site-lisp/notmuch-show.el
notmuch-git /usr/share/emacs/site-lisp/notmuch-show.elc
notmuch-git /usr/share/emacs/site-lisp/notmuch-wash.el
notmuch-git /usr/share/emacs/site-lisp/notmuch-wash.elc
notmuch-git /usr/share/emacs/site-lisp/notmuch.el
notmuch-git /usr/share/emacs/site-lisp/notmuch.elc
notmuch-git /usr/share/man/
notmuch-git /usr/share/man/man1/
notmuch-git /usr/share/man/man1/notmuch.1.gz
notmuch-git /usr/share/vim/
notmuch-git /usr/share/vim/vimfiles/
notmuch-git /usr/share/vim/vimfiles/plugin/
notmuch-git /usr/share/vim/vimfiles/plugin/notmuch.vim
notmuch-git /usr/share/vim/vimfiles/syntax/
notmuch-git /usr/share/vim/vimfiles/syntax/notmuch-compose.vim
notmuch-git /usr/share/vim/vimfiles/syntax/notmuch-folders.vim
notmuch-git /usr/share/vim/vimfiles/syntax/notmuch-git-diff.vim
notmuch-git /usr/share/vim/vimfiles/syntax/notmuch-search.vim
notmuch-git /usr/share/vim/vimfiles/syntax/notmuch-show.vim
notmuch-git /usr/share/zsh/
notmuch-git /usr/share/zsh/functions/
notmuch-git /usr/share/zsh/functions/Completion/
notmuch-git /usr/share/zsh/functions/Completion/Unix/
notmuch-git /usr/share/zsh/functions/Completion/Unix/_notmuch

and I checked there were no lingering .el files...

so...
 any way to tell which notmuch-emacs-ui I am actually using ? (I am a newbie
when comes to hacking lisp)

-s

[-- Attachment #2: Type: text/html, Size: 4540 bytes --]

Re: bug in emacs-ui ?

[Jameson Graef Rollins]

[-- Attachment #1: Type: text/plain, Size: 714 bytes --]

On Tue, 21 Jun 2011 02:01:17 +0200, Sebastien Binet <seb.binet@gmail.com> wrote:
> and I checked there were no lingering .el files...
> 
> so...
>  any way to tell which notmuch-emacs-ui I am actually using ? (I am a newbie
> when comes to hacking lisp)

Hey, Sebastien.  You can determine the loaded version of a library from
within emacs with the follow command:

M-x locate-library notmuch

It's also good to know how many notmuch instances are installed on your
system.  For instance, I have a system-wide installation, a "personal"
installation, the build currently in the source tree, etc.  Depending on
the options I supply to emacs at startup, I could run a variety of
versions.

jamie.

[-- Attachment #2: Type: application/pgp-signature, Size: 835 bytes --]

Re: bug in emacs-ui ?

[Sebastien Binet]

[-- Attachment #1: Type: text/plain, Size: 1307 bytes --]

On Mon, 20 Jun 2011 22:41:18 -0700, Jameson Graef Rollins <jrollins@finestructure.net> wrote:
Non-text part: multipart/signed
> On Tue, 21 Jun 2011 02:01:17 +0200, Sebastien Binet <seb.binet@gmail.com> wrote:
> > and I checked there were no lingering .el files...
> > 
> > so...
> >  any way to tell which notmuch-emacs-ui I am actually using ? (I am a newbie
> > when comes to hacking lisp)
> 
> Hey, Sebastien.  You can determine the loaded version of a library from
> within emacs with the follow command:
> 
> M-x locate-library notmuch
which points to the system-wide one.

> 
> It's also good to know how many notmuch instances are installed on your
> system.  For instance, I have a system-wide installation, a "personal"
> installation, the build currently in the source tree, etc.  Depending on
> the options I supply to emacs at startup, I could run a variety of
> versions.
being root and having this great ArchLinux package manager system at my
finger tips, I only have one installation of notmuch :)

playing a bit more, I cloned your 0.6 branch, cloned the official one,
slammed the 0.6/emacs directory on top of the official one, built the
official one, installed it and everything worked.

I am trying to see which changeset is the source of my problem...

-s

[-- Attachment #2: Type: application/pgp-signature, Size: 197 bytes --]

Re: bug in emacs-ui ?

[Sebastien Binet]

[-- Attachment #1: Type: text/plain, Size: 3301 bytes --]

hi,

On Mon, 20 Jun 2011 22:41:18 -0700, Jameson Graef Rollins <jrollins@finestructure.net> wrote:
Non-text part: multipart/signed
> On Tue, 21 Jun 2011 02:01:17 +0200, Sebastien Binet <seb.binet@gmail.com> wrote:
> > and I checked there were no lingering .el files...
> > 
> > so...
> >  any way to tell which notmuch-emacs-ui I am actually using ? (I am a newbie
> > when comes to hacking lisp)
> 
> Hey, Sebastien.  You can determine the loaded version of a library from
> within emacs with the follow command:
> 
> M-x locate-library notmuch
> 
> It's also good to know how many notmuch instances are installed on your
> system.  For instance, I have a system-wide installation, a "personal"
> installation, the build currently in the source tree, etc.  Depending on
> the options I supply to emacs at startup, I could run a variety of
> versions.

so, it seems the problem comes from:

(defun notmuch-show-advance-and-archive ()
  "Advance through thread and archive."
  (interactive)
  (let ((end-of-this-message (notmuch-show-message-bottom)))
    (cond
     ;; Ideally we would test `end-of-this-message' against the result
     ;; of `window-end', but that doesn't account for the fact that
     ;; the end of the message might be hidden, so we have to actually
     ;; go to the end, walk back over invisible text and then see if
     ;; point is visible.
     ((save-excursion
        (message "pt00: %s" (point))
        (goto-char (- end-of-this-message 1))
        (message "pt01: %s" (point))
        (notmuch-show-move-past-invisible-backward)
        (message "msg-end: %s" end-of-this-message)
        (message "pt11: %s" (point))
        ;;(goto-char (- (point) 400))
        (message "pt12: %s" (point))
        (> (point) (window-end)))
      (message "point: %s" (point))
      (message "window-end: %s" (window-end))
      ;; The bottom of this message is not visible - scroll.
      (scroll-up nil))
     ((not (= end-of-this-message (point-max)))
      ;; This is not the last message - move to the next visible one.
      (notmuch-show-next-open-message))

where I've added some good ol' print "foo" debugging.

using the message from the openmpi mailing list I sent earlier and
pressing tab, I get in the *Messages* buffer:

For information about GNU Emacs and the GNU system, type C-h C-a.
pt00: 1
pt01: 1392
msg-end: #<marker at 1393 in *[Open MPI Announce] Open MPI...>
pt11: 1392
pt12: 1392
point: 1
window-end: 1113
notmuch-show-advance-and-archive: End of buffer                                                                                                                                                                                            
ie: it would seem the notmuch-show-move-past-invisible-backward does
*not* move the point up to just before the hidden signature (and does
not move it at all.)

if I uncomment the goto-char to -400 line, everything's fine. (400 is
roughly the length of the hidden signature)

well, this is just an educated guess from an emacs-lisp programmer
complete newbie.

fyi: I am using emacs-23.3
no patch were applied on top of the vanilla sources:
http://projects.archlinux.org/svntogit/packages.git/tree/emacs/repos/extra-x86_64/PKGBUILD

-s

[-- Attachment #2: Type: application/pgp-signature, Size: 197 bytes --]

Re: bug in emacs-ui ?

[Carl Worth]

[-- Attachment #1: Type: text/plain, Size: 269 bytes --]

On Tue, 21 Jun 2011 21:26:25 +0200, Sebastien Binet <seb.binet@gmail.com> wrote:
> fyi: I am using emacs-23.3

Perhaps this is an emacs bug?

I'm using Debian's emacs 23.3.1 and have not encountered the problem
described.

-Carl

-- 
carl.d.worth@intel.com

[-- Attachment #2: Type: application/pgp-signature, Size: 197 bytes --]

Re: bug in emacs-ui ?

[Sebastien Binet]

[-- Attachment #1: Type: text/plain, Size: 734 bytes --]

On Tue, 21 Jun 2011 15:09:20 -0700, Carl Worth <cworth@cworth.org> wrote:
Non-text part: multipart/signed
> On Tue, 21 Jun 2011 21:26:25 +0200, Sebastien Binet <seb.binet@gmail.com> wrote:
> > fyi: I am using emacs-23.3
> 
> Perhaps this is an emacs bug?
could be, but,

> I'm using Debian's emacs 23.3.1 and have not encountered the problem
> described.
I don't see anything related to 'point', 'point-invisible-p' nor 'forward-char' in there:
http://patch-tracker.debian.org/package/emacs23/23.3+1-1

anyways... for the moment I'll just live with it...
except if somebody has some insights on how to "catch" the 'End of
buffer' error and add some more protective programming around the
'scroll-up' function ?

-s

[-- Attachment #2: Type: application/pgp-signature, Size: 197 bytes --]

Re: bug in emacs-ui ?

[Carl Worth]

[-- Attachment #1: Type: text/plain, Size: 1080 bytes --]

On Wed, 22 Jun 2011 08:50:23 +0200, Sebastien Binet <seb.binet@gmail.com> wrote:
> On Tue, 21 Jun 2011 15:09:20 -0700, Carl Worth <cworth@cworth.org> wrote:
> > Perhaps this is an emacs bug?
> could be, but,
> 
> > I'm using Debian's emacs 23.3.1 and have not encountered the problem
> > described.
> I don't see anything related to 'point', 'point-invisible-p' nor 'forward-char' in there:
> http://patch-tracker.debian.org/package/emacs23/23.3+1-1

Perhaps I was confused. I thought 23.3.1 was a distinct upstream release
From 23.3, but maybe not, (emacs version numbers use 1-based indexing
perhaps?).

> anyways... for the moment I'll just live with it...

Sorry about that.

> except if somebody has some insights on how to "catch" the 'End of
> buffer' error and add some more protective programming around the
> 'scroll-up' function ?

My emacs lisp skills are primarily restricted to actual
experimentation. So if I can replicate the bug, I might be able to find
a fix. I'm not very good at doing theoretical fixes with emacs lisp
code.

-Carl

[-- Attachment #2: Type: application/pgp-signature, Size: 197 bytes --]

Re: bug in emacs-ui ?

[Jani Nikula]

Carl Worth <cworth@...> writes:

> 
> On Wed, 22 Jun 2011 08:50:23 +0200, Sebastien Binet
> <seb.binet@...> wrote:
> > On Tue, 21 Jun 2011 15:09:20 -0700, Carl Worth <cworth@...> wrote:
> > > Perhaps this is an emacs bug?
> > could be, but,
> > 
> > > I'm using Debian's emacs 23.3.1 and have not encountered the problem
> > > described.
> > I don't see anything related to 'point', 'point-invisible-p' nor
'forward-char' in there:
> > http://patch-tracker.debian.org/package/emacs23/23.3+1-1
> 
> Perhaps I was confused. I thought 23.3.1 was a distinct upstream release
> From 23.3, but maybe not, (emacs version numbers use 1-based indexing
> perhaps?).
> 
> > anyways... for the moment I'll just live with it...
> 
> Sorry about that.
> 
> > except if somebody has some insights on how to "catch" the 'End of
> > buffer' error and add some more protective programming around the
> > 'scroll-up' function ?
> 
> My emacs lisp skills are primarily restricted to actual
> experimentation. So if I can replicate the bug, I might be able to find
> a fix. I'm not very good at doing theoretical fixes with emacs lisp
> code.

I bisected the problem to commit 95ef8da29439f2e79115c36ab4d2a80aef1a1462 ("Fix
hiding a message while some citations are shown in notmuch-show view").
Reverting that fixes the problem for me. (If you don't want to resolve
conflicts, also revert 432e091924c1d1d8950a44ca78bc5b9c5ade47e4 first.) I don't
have the time just now to try to figure out the problem in that, but perhaps
this will help others go forward.

Jani

Re: bug in emacs-ui ?

[Dmitry Kurochkin]

Hi Jani.

On Tue, 28 Jun 2011 10:35:48 +0000 (UTC), Jani Nikula <jani@nikula.org> wrote:
> Carl Worth <cworth@...> writes:
> 
> > 
> > On Wed, 22 Jun 2011 08:50:23 +0200, Sebastien Binet
> > <seb.binet@...> wrote:
> > > On Tue, 21 Jun 2011 15:09:20 -0700, Carl Worth <cworth@...> wrote:
> > > > Perhaps this is an emacs bug?
> > > could be, but,
> > > 
> > > > I'm using Debian's emacs 23.3.1 and have not encountered the problem
> > > > described.
> > > I don't see anything related to 'point', 'point-invisible-p' nor
> 'forward-char' in there:
> > > http://patch-tracker.debian.org/package/emacs23/23.3+1-1
> > 
> > Perhaps I was confused. I thought 23.3.1 was a distinct upstream release
> > From 23.3, but maybe not, (emacs version numbers use 1-based indexing
> > perhaps?).
> > 
> > > anyways... for the moment I'll just live with it...
> > 
> > Sorry about that.
> > 
> > > except if somebody has some insights on how to "catch" the 'End of
> > > buffer' error and add some more protective programming around the
> > > 'scroll-up' function ?
> > 
> > My emacs lisp skills are primarily restricted to actual
> > experimentation. So if I can replicate the bug, I might be able to find
> > a fix. I'm not very good at doing theoretical fixes with emacs lisp
> > code.
> 
> I bisected the problem to commit 95ef8da29439f2e79115c36ab4d2a80aef1a1462 ("Fix
> hiding a message while some citations are shown in notmuch-show view").
> Reverting that fixes the problem for me. (If you don't want to resolve
> conflicts, also revert 432e091924c1d1d8950a44ca78bc5b9c5ade47e4 first.) I don't
> have the time just now to try to figure out the problem in that, but perhaps
> this will help others go forward.
> 

Thanks for tracking this.  I will look into it.

Regards,
  Dmitry

> Jani
> 
> 
> _______________________________________________
> notmuch mailing list
> notmuch@notmuchmail.org
> http://notmuchmail.org/mailman/listinfo/notmuch

Re: bug in emacs-ui ?

[Dmitry Kurochkin]

On Tue, 28 Jun 2011 21:38:17 +0400, Dmitry Kurochkin <dmitry.kurochkin@gmail.com> wrote:
> Hi Jani.
> 
> On Tue, 28 Jun 2011 10:35:48 +0000 (UTC), Jani Nikula <jani@nikula.org> wrote:
> > Carl Worth <cworth@...> writes:
> > 
> > > 
> > > On Wed, 22 Jun 2011 08:50:23 +0200, Sebastien Binet
> > > <seb.binet@...> wrote:
> > > > On Tue, 21 Jun 2011 15:09:20 -0700, Carl Worth <cworth@...> wrote:
> > > > > Perhaps this is an emacs bug?
> > > > could be, but,
> > > > 
> > > > > I'm using Debian's emacs 23.3.1 and have not encountered the problem
> > > > > described.
> > > > I don't see anything related to 'point', 'point-invisible-p' nor
> > 'forward-char' in there:
> > > > http://patch-tracker.debian.org/package/emacs23/23.3+1-1
> > > 
> > > Perhaps I was confused. I thought 23.3.1 was a distinct upstream release
> > > From 23.3, but maybe not, (emacs version numbers use 1-based indexing
> > > perhaps?).
> > > 
> > > > anyways... for the moment I'll just live with it...
> > > 
> > > Sorry about that.
> > > 
> > > > except if somebody has some insights on how to "catch" the 'End of
> > > > buffer' error and add some more protective programming around the
> > > > 'scroll-up' function ?
> > > 
> > > My emacs lisp skills are primarily restricted to actual
> > > experimentation. So if I can replicate the bug, I might be able to find
> > > a fix. I'm not very good at doing theoretical fixes with emacs lisp
> > > code.
> > 
> > I bisected the problem to commit 95ef8da29439f2e79115c36ab4d2a80aef1a1462 ("Fix
> > hiding a message while some citations are shown in notmuch-show view").
> > Reverting that fixes the problem for me. (If you don't want to resolve
> > conflicts, also revert 432e091924c1d1d8950a44ca78bc5b9c5ade47e4 first.) I don't
> > have the time just now to try to figure out the problem in that, but perhaps
> > this will help others go forward.
> > 
> 
> Thanks for tracking this.  I will look into it.
> 

I have posted a patch to fix this bug [1].

Regards,
  Dmitry

[1] id:"1309312132-14564-2-git-send-email-dmitry.kurochkin@gmail.com"

> Regards,
>   Dmitry
> 
> > Jani
> > 
> > 
> > _______________________________________________
> > notmuch mailing list
> > notmuch@notmuchmail.org
> > http://notmuchmail.org/mailman/listinfo/notmuch

Re: bug in emacs-ui ?

[Sebastien Binet]

[-- Attachment #1: Type: text/plain, Size: 2295 bytes --]

Dmitry,

On Wed, 29 Jun 2011 05:53:37 +0400, Dmitry Kurochkin <dmitry.kurochkin@gmail.com> wrote:
> On Tue, 28 Jun 2011 21:38:17 +0400, Dmitry Kurochkin <dmitry.kurochkin@gmail.com> wrote:
> > Hi Jani.
> > 
> > On Tue, 28 Jun 2011 10:35:48 +0000 (UTC), Jani Nikula <jani@nikula.org> wrote:
> > > Carl Worth <cworth@...> writes:
> > > 
> > > > 
> > > > On Wed, 22 Jun 2011 08:50:23 +0200, Sebastien Binet
> > > > <seb.binet@...> wrote:
> > > > > On Tue, 21 Jun 2011 15:09:20 -0700, Carl Worth <cworth@...> wrote:
> > > > > > Perhaps this is an emacs bug?
> > > > > could be, but,
> > > > > 
> > > > > > I'm using Debian's emacs 23.3.1 and have not encountered the problem
> > > > > > described.
> > > > > I don't see anything related to 'point', 'point-invisible-p' nor
> > > 'forward-char' in there:
> > > > > http://patch-tracker.debian.org/package/emacs23/23.3+1-1
> > > > 
> > > > Perhaps I was confused. I thought 23.3.1 was a distinct upstream release
> > > > From 23.3, but maybe not, (emacs version numbers use 1-based indexing
> > > > perhaps?).
> > > > 
> > > > > anyways... for the moment I'll just live with it...
> > > > 
> > > > Sorry about that.
> > > > 
> > > > > except if somebody has some insights on how to "catch" the 'End of
> > > > > buffer' error and add some more protective programming around the
> > > > > 'scroll-up' function ?
> > > > 
> > > > My emacs lisp skills are primarily restricted to actual
> > > > experimentation. So if I can replicate the bug, I might be able to find
> > > > a fix. I'm not very good at doing theoretical fixes with emacs lisp
> > > > code.
> > > 
> > > I bisected the problem to commit 95ef8da29439f2e79115c36ab4d2a80aef1a1462 ("Fix
> > > hiding a message while some citations are shown in notmuch-show view").
> > > Reverting that fixes the problem for me. (If you don't want to resolve
> > > conflicts, also revert 432e091924c1d1d8950a44ca78bc5b9c5ade47e4 first.) I don't
> > > have the time just now to try to figure out the problem in that, but perhaps
> > > this will help others go forward.
> > > 
> > 
> > Thanks for tracking this.  I will look into it.
> > 
> 
> I have posted a patch to fix this bug [1].

thanks a lot for figuring this one out.
I'll give it a try!

-s


[-- Attachment #2: Type: application/pgp-signature, Size: 197 bytes --]