Gnus development mailing list
 help / color / mirror / Atom feed
From: Raymond Scholz <ray-2002@zonix.de>
Subject: Re: Cry for help: deuglify.el - moving stuff in the Article Buffer
Date: Sun, 29 Dec 2002 01:24:27 +0100	[thread overview]
Message-ID: <gd.871y41smdg.fsf@mde1.zonix.de> (raw)
In-Reply-To: <m3ptrl7oy0.fsf@quimbies.gnus.org>

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

* Lars Magne Ingebrigtsen <larsi@gnus.org> wrote:

> Raymond Scholz <ray-2002@zonix.de> writes:
>
>> If you're using `W k' to deuglify messages, you may have encountered
>> the problem that messages with MIME parts (or format=flowed)
>> completely disappear from the Article Buffer.  This is due to the
>> brain-dead implementation of `gnus-outlook-rearrange-article'
>
> Could you construct a message that displays this behavior?

I've attached a real world example.

I was tryig to fix this a few weeks ago but did not suceed in any
way :(  

The call to `gnus-article-prepare-display'  in
`gnus-article-outlook-deuglify-article' is the cause of the
disappearance but commenting it out means, no highlighting will be
done after repairing the article.

Another drawback of deuglify.el is that
`gnus-outlook-rearrange-article' tempers the kill ring.  I've tried to
fix this (see the commented out function below).  Again - no luck.

--- lisp/deuglify.el	2002/12/28 23:54:45	6.4
+++ lisp/deuglify.el	2002/12/29 00:17:54
@@ -325,6 +325,30 @@
 	  (yank)
 	  (insert "\n"))))))
 
+;; Trying not to temper the kill ring - does not work...
+;;
+;; (defun gnus-outlook-rearrange-article (from-where)
+;;   "Put the text from `from-where' to the end of buffer at the top of
+;; the article buffer."
+;;   (save-excursion
+;;     (let ((inhibit-read-only t)
+;; 	  (cite-marks gnus-outlook-deuglify-cite-marks))
+;;       (gnus-with-article-buffer
+;; 	(setq tmp-point (point))
+;; 	(beginning-of-buffer)
+;; 	(setq body-point-min (point))
+;; 	(goto-char from-where)
+;; 	(beginning-of-line)
+;; 	(setq citation-min (point))
+;; 	(goto-char tmp-point)
+;; 	(gnus-message 3 "%s-%s <-> %s-%s"
+;; 		      citation-min (point-max) body-point-min (- citation-min 1))
+;; 	(unless (search-forward-regexp
+;; 		 (concat "^[ \t]*[^" cite-marks "\n]") nil t)
+;; 	  (transpose-regions citation-min (point-max)
+;; 			     body-point-min (- citation-min 1)))))))
+
+
 ;; John Doe <john.doe@some.domain> wrote in message
 ;; news:a87usw8$dklsssa$2@some.news.server...
 
@@ -423,9 +447,9 @@
 (defun gnus-article-outlook-deuglify-article ()
   "Deuglify broken Outlook (Express) articles and redisplay."
   (interactive)
-  (gnus-outlook-deuglify-article)
-  (with-current-buffer (or gnus-article-buffer (current-buffer))
-    (gnus-article-prepare-display)))
+  (gnus-outlook-deuglify-article))
+;;   (with-current-buffer (or gnus-article-buffer (current-buffer))
+;;     (gnus-article-prepare-display)))
 
 (provide 'deuglify)

Cheers, Ray
-- 
Q: What have american beer and sex in a canoe in common?
A: Both are fucking close to water.

[-- Attachment #2: format-flowed.msg --]
[-- Type: application/octet-stream, Size: 1576 bytes --]

Path: informatik.uni-bremen.de!cs.tu-berlin.de!fu-berlin.de!uni-berlin.de!pop-zh-12-1-dialup-3.freesurf.CH!not-for-mail
From: scheidegger <rscheidegger@gmx.ch>
Newsgroups: alt.comp.periphs.mainboard.asus
Subject: Re: P2B cpu Upgrade
Date: Sat, 29 Dec 2001 23:50:17 +0100
Message-ID: <3C2E48A9.8070100@gmx.ch>
References: <a0ko0d$5ae$1@helle.btinternet.com>
NNTP-Posting-Host: pop-zh-12-1-dialup-3.freesurf.ch (194.230.198.3)
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-Trace: fu-berlin.de 1009666186 22569474 194.230.198.3 (16 [84205])
User-Agent: Mozilla/5.0 (Windows; U; Win98; en-US; rv:0.9.7) Gecko/20011221
X-Accept-Language: de-CH, de, en
Xref: mde1.home mail.zoo:29
Lines: 22

Chris wrote:

> I have ASUS P2B rev 1.02 with PII 400mhz 100FSB. What is best cpu upgrade I
> can hope for ? Would a SECC2 Slot 1 PIII  work in this old Slot 1 m'board?
> Thanks for any help- I am new to this
> Chris
> 


No, a slot1 cpu will not work, regardless what other people said!
(that's not exactly true, the old (katmai) PIII with 512KB cache 
(available up to 600Mhz) will work fine.)
You need a fcpga (coppermine) compatible slotket adapter that has 
voltage adjustment jumpers (like the asus s370-dl), and your board will 
take all 100Mhz FSB cpus up to 1 Ghz (celeron or PIII), but not the 
1.1Ghz versions (bios bug) and nothing faster than 1.1Ghz neither (those 
are tualatins, not compatible at all).
Unfortunately, slotkets seem to be hard to find nowadays...
You'll probably have to look on ebay.

Roland



  reply	other threads:[~2002-12-29  0:24 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-10-16 19:37 Raymond Scholz
2002-12-28 22:34 ` Lars Magne Ingebrigtsen
2002-12-29  0:24   ` Raymond Scholz [this message]
2002-12-29 14:33     ` Lars Magne Ingebrigtsen
2002-12-29 20:26       ` Raymond Scholz
2002-12-29 22:56         ` Lars Magne Ingebrigtsen
2002-12-29 23:35           ` Raymond Scholz
2003-01-01 18:54             ` Lars Magne Ingebrigtsen
2003-01-02 10:32               ` Raymond Scholz
2002-12-30 12:33           ` Raymond Scholz
2002-12-30 12:53           ` Raymond Scholz
2002-12-31  0:11   ` Raymond Scholz
2002-12-31  0:37     ` Lars Magne Ingebrigtsen
2002-12-31 16:38       ` Raymond Scholz

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=gd.871y41smdg.fsf@mde1.zonix.de \
    --to=ray-2002@zonix.de \
    --cc=rscholz@zonix.de \
    /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 NNTP newsgroup(s).