unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: "Davis Herring" <herring@lanl.gov>
To: "John Owens" <john_owens@yahoo.com>
Cc: emacs-devel@gnu.org
Subject: Re: filladapt mode stops filling after lengthy amount  of	emacs	uptime
Date: Thu, 29 Mar 2007 10:35:49 -0700 (PDT)	[thread overview]
Message-ID: <46214.128.165.123.18.1175189749.squirrel@webmail.lanl.gov> (raw)
In-Reply-To: <loom.20070329T190902-688@post.gmane.org>

> More possibly the culprit is the MIME editing facility in SEMI, the MIME
> handling library (used in my mailer Wanderlust). In it:
>
> (defun turn-on-mime-edit ()
>     ...
>     (setq paragraph-start
> 	  (regexp-or mime-edit-single-part-tag-regexp
> 		     paragraph-start))
>
> Here's that regexp.
>
> (defconst mime-edit-single-part-tag-regexp
>   "--[[][[]\\([^]]*\\)]\\([[]\\([^]]*\\)]\\|\\)]"
>   "*Regexp of MIME tag in the form of [[CONTENT-TYPE][ENCODING]].")
>
> Does that seem like it might be the problem? (SEMI's problem?)

That sounds very much like the problem, like `turn-on-mime-edit' is
getting called repeatedly in the same buffer.  Try adding

(message "turn-on-mime-edit(buffer=%s,pslen=%s)"
         (current-buffer) (length paragraph-start))

to that function (evaluating the `defun' after that library has been
loaded, of course).  Then you can test this hypothesis.  If it is being
called repeatedly, either there is a bug elsewhere that calls it when it's
not necessary, or that function should be modified to only modify
paragraph-start if it has not done so already (perhaps by setting a flag
or consulting the existing value).

Davis

-- 
This product is sold by volume, not by mass.  If it appears too dense or
too sparse, it is because mass-energy conversion has occurred during
shipping.

  reply	other threads:[~2007-03-29 17:35 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-03-22  5:22 filladapt mode stops filling after lengthy amount of emacs uptime John Owens
2007-03-22 14:49 ` Chong Yidong
2007-03-29  5:03   ` John Owens
2007-03-29 13:53     ` Stefan Monnier
2007-03-29 15:57       ` Chong Yidong
2007-03-29 17:13         ` John Owens
2007-03-29 17:35           ` Davis Herring [this message]
2007-03-29 17:45           ` Chong Yidong
2007-03-30  0:43           ` Stefan Monnier
2007-03-30 11:02             ` Andreas Schwab
2007-03-30 16:10               ` Stefan Monnier
2007-03-31 19:05                 ` Michael Olson
2007-03-29 14:21     ` Davis Herring
2007-03-29 18:00       ` Richard Stallman
2007-03-29 18:05         ` Davis Herring
2007-03-29 18:29           ` David Kastrup
2007-03-29 20:35             ` Davis Herring
2007-03-30 12:42           ` Richard Stallman
2007-03-29 18:16         ` John Owens
2007-03-22 22:50 ` Richard Stallman
2007-04-06 17:36 ` John Owens
2007-04-06 18:18   ` 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=46214.128.165.123.18.1175189749.squirrel@webmail.lanl.gov \
    --to=herring@lanl.gov \
    --cc=emacs-devel@gnu.org \
    --cc=john_owens@yahoo.com \
    /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).