From: David Hansen <david.hansen@gmx.net>
Subject: Re: [david.hansen@physik.fu-berlin.de: WoMan Bug]
Date: Sat, 23 Sep 2006 06:38:22 +0200 [thread overview]
Message-ID: <87ac4r9ozl.fsf@robotron.kosmorama> (raw)
In-Reply-To: 87y7scpptc.fsf@furball.mit.edu
On Thu, 21 Sep 2006 23:01:35 -0400 Chong Yidong wrote:
> David Hansen <david.hansen@gmx.net> writes:
>
>> On Sat, 16 Sep 2006 13:58:39 -0400 Stefan Monnier wrote:
>>
>>> I believe the patch below catches all the places where the problem could
>>> have shown up. Can someone check that it makes sense and works?
>>
>> Hmm, against which version of woman i have to apply this
>> patch? Can't get it to work with a fresh updated emacs.
>
> Works for me.
I doubt. It even has unbalanced parens. But with a patched
patch it's rendering the screen man page (please check. I
only did the obvious stuff to get it compiled w/o warnings).
*** /home/dhansen/.emacs.d/saves/!home!dhansen!woman.el.~1~ 2006-09-23 06:10:16.000000000 +0200
--- /home/dhansen/share/emacs/22.0.50/lisp/woman.el 2006-09-23 06:24:46.000000000 +0200
***************
*** 2657,2665 ****
(error "File `%s' not found" name))
(beginning-of-line)
(woman-delete-line 1)
! (let ((from (point))
! (length (woman-insert-file-contents filename 0))
! (to (copy-marker (+ from length) t)))
(woman-pre-process-region from to)
(set-marker to nil)
(goto-char from)
--- 2657,2665 ----
(error "File `%s' not found" name))
(beginning-of-line)
(woman-delete-line 1)
! (let* ((from (point))
! (length (woman-insert-file-contents filename 0))
! (to (copy-marker (+ from length) t)))
(woman-pre-process-region from to)
(set-marker to nil)
(goto-char from)
***************
*** 3971,3984 ****
(delete-char 1)
(looking-at "\\(.\\)\\(.*\\)\\1")
(forward-char 1)
! (let* ((to (match-end 2)))
(from (match-beginning 0))
(N (woman-parse-numeric-arg))
(c (if (< (point) to) (following-char) ?_)))
(delete-region from to)
(delete-char 1)
! (insert (make-string N c))
! ))
;;; 4. Text Filling, Adjusting, and Centering
--- 3971,3983 ----
(delete-char 1)
(looking-at "\\(.\\)\\(.*\\)\\1")
(forward-char 1)
! (let* ((to (match-end 2))
(from (match-beginning 0))
(N (woman-parse-numeric-arg))
(c (if (< (point) to) (following-char) ?_)))
(delete-region from to)
(delete-char 1)
! (insert (make-string N c))))
;;; 4. Text Filling, Adjusting, and Centering
next prev parent reply other threads:[~2006-09-23 4:38 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-14 2:34 [david.hansen@physik.fu-berlin.de: WoMan Bug] Richard Stallman
2006-09-14 4:43 ` Michael Welsh Duggan
2006-09-14 5:36 ` Stefan Monnier
2006-09-14 17:00 ` David Hansen
2006-09-15 5:34 ` Michael Welsh Duggan
2006-09-15 5:58 ` Michael Welsh Duggan
2006-09-16 17:58 ` Stefan Monnier
2006-09-18 15:51 ` Chong Yidong
2006-09-18 23:11 ` David Hansen
2006-09-22 3:01 ` Chong Yidong
2006-09-22 17:01 ` Richard Stallman
2006-09-23 4:38 ` David Hansen [this message]
2006-09-15 5:52 ` Michael Welsh Duggan
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=87ac4r9ozl.fsf@robotron.kosmorama \
--to=david.hansen@gmx.net \
/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).