unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: David Golden <david.golden@oceanfree.net>
To: emacs-pretest-bug@gnu.org
Subject: Re: 23.0.60;	rmail-redecode-body finishing with error "Invalid Search Bound"
Date: Wed, 16 Jan 2008 17:57:17 +0000	[thread overview]
Message-ID: <200801161757.17982.david.golden@oceanfree.net> (raw)
In-Reply-To: <200801161633.44000.david.golden@oceanfree.net>

On Wednesday 16 January 2008, David Golden wrote:
> On Wednesday 16 January 2008, martin rudalics wrote:
> > With your rmail.redecode I get on my system
>
> Just to check: your system ==> emacs-unicode-2 or cvs head or...?
>
> > at =1=> for `point' the value 223 and for `end' 1146
> > at =2=> for `beg' 183 and for `point' 871
> >
> > hence it doesn't fail for me.  Since it apparently fails at =1=>
> > for you could you please tell me the values for `point' and `end'
> > there?
>
> (point)  :  224
> end: 190
>
> [and beg: 183]
>
> Soo... Indeed end is before point.
>
> in (let ((end (rmail-msgend n)))  in rmail-show-message [line 2800]
> (rmail-msgend n) is returning 190, which seems, well, wrong.
> (n is 1).
>


When rmail-msgend is returning 190 (i.e. when called by 
rmail-show-message called by rmail-redecode-body), rmail-message-vector 
itself seems to have markers at 1,183,190 instead of 1,183,1176 in it.

In rmail-redecode-body, perhaps suspiciously

		    (goto-char x-coding-header)
		    (delete-region (point)
				   (save-excursion
				     (beginning-of-line)
				     (point)))
		    (insert "X-Coding-System: "
			    (symbol-name last-coding-system-used))
===>		    (set-marker x-coding-header nil) 

x-coding-header happens to have a value #<marker at 190 in RMAIL>

  parent reply	other threads:[~2008-01-16 17:57 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-01-07  4:21 23.0.60; rmail-redecode-body finishing with error "Invalid Search Bound" David Golden
2008-01-10  4:09 ` Richard Stallman
2008-01-10 18:36   ` David Golden
2008-01-11 13:59     ` Richard Stallman
2008-01-12 16:05       ` Eli Zaretskii
2008-01-15 17:42     ` martin rudalics
2008-01-16  4:02       ` David Golden
2008-01-16  7:34         ` martin rudalics
2008-01-16 16:33           ` David Golden
2008-01-16 17:03             ` martin rudalics
2008-01-16 17:57             ` David Golden [this message]
2008-01-16 19:30               ` David Golden
2008-01-16 19:56                 ` martin rudalics
2008-01-16 20:36                   ` David Golden
2008-01-16 21:18                     ` martin rudalics
2008-01-16 21:34                       ` David Golden
2008-01-16 22:11                         ` martin rudalics
2008-01-17  7:47                         ` martin rudalics
2008-01-17 17:04                           ` Stefan Monnier
2008-01-17 18:50                             ` martin rudalics
2008-01-18  7:18                             ` Kenichi Handa
2008-01-18 20:19                               ` David Golden
2008-01-16 19:34               ` martin rudalics

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=200801161757.17982.david.golden@oceanfree.net \
    --to=david.golden@oceanfree.net \
    --cc=emacs-pretest-bug@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.
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).