Gnus development mailing list
 help / color / mirror / Atom feed
From: Karl Kleinpaste <karl@jprc.com>
Subject: Re: Functional complaint, customize library
Date: 07 Apr 1998 19:40:06 -0400	[thread overview]
Message-ID: <vxku385ciax.fsf@pocari-sweat.jprc.com> (raw)
In-Reply-To: Stainless Steel Rat's message of "07 Apr 1998 17:54:58 -0400"

Stainless Steel Rat <ratinox@peorth.gweep.net> writes:
> The patch has worked against all version of cus-face since back in the Red
> Gnus development cycle right up to the current version, 1.996 or so, at
> least as far as I have been able to determine.  Just use your handy-dandy
> "patch" as with any other context diff.

Maybe you should contemplate reading my entire note, specifically:

: Whap me once hard with a clue hammer if need be, but (e.g.) the symbol
: custom-get-frame-properties does not occur anywhere in any of the
: custom/cus*.el files in my installation, and PATCH(1) IS UNDERSTANDABLY
: RELUCTANT TO HELP.

Note transcript:

pocari-sweat: patch cus-face.el < ../Mail/list/ding/16443
Hmm...  Looks like a new-style context diff to me...
The text leading up to this was:
--------------------------
	[ deletia of mail headers &c. ]
|
|Hooray, custom.
|
|This alone is the first half-dozen reasons why I don't like it.  Which is
|why I use this patch against cus-face.el:
|
|*** cus-face.el.orig   Sat Sep 13 09:43:22 1997
|- --- cus-face.el      Sun Sep 21 00:02:28 1997
--------------------------
Patching file cus-face.el using Plan A...
patch: **** unexpected end of hunk at line 71
pocari-sweat: echo $?
1
pocari-sweat: grep custom-get-frame-properties cus-face.el 
pocari-sweat: grep -i version custom.el
;; Version: 1.9960-x
;; the Free Software Foundation; either version 2, or (at your option)
;; any later version.
  ;; Maybe this option was rogue in an earlier version.  It no longer is.
pocari-sweat: 

Considering that your patch references line 470 in cus-face.el, and my 
cus-face.el is only 255 lines long, it's just possible that one of our 
versions is out of date.  I've stipulated the version I'm using above,
which appears to be later than yours.  Notably, as the grep above
shows, your patch contains references to symbols which simply do not
exist in the version I've got.

My system also has FSFmacs 20.2 installed, whose cus-face.el is only
172 lines long, in which custom.el claims to be version 1.9900.


  parent reply	other threads:[~1998-04-07 23:40 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1998-04-07 14:24 Karl Kleinpaste
1998-04-07 15:30 ` Per Abrahamsen
     [not found]   ` <x7lnth4ewy.fsf@peorth.gweep.net>
1998-04-07 22:08     ` Hrvoje Niksic
     [not found]       ` <x7d8et1buq.fsf@peorth.gweep.net>
1998-04-08 10:05         ` Per Abrahamsen
1998-04-08 10:05     ` Per Abrahamsen
1998-04-07 16:28 ` Scott Blachowicz
     [not found] ` <x7ogyd4ez4.fsf@peorth.gweep.net>
1998-04-07 21:31   ` Karl Kleinpaste
     [not found]     ` <x7iuol1eml.fsf@peorth.gweep.net>
1998-04-07 23:40       ` Karl Kleinpaste [this message]
     [not found]         ` <x7vhslvy0k.fsf@peorth.gweep.net>
1998-04-08  2:46           ` Hrvoje Niksic
1998-04-08 18:57             ` Jake Colman
1998-04-08 21:03               ` Alan Shutko
1998-04-09 11:26               ` Hrvoje Niksic

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=vxku385ciax.fsf@pocari-sweat.jprc.com \
    --to=karl@jprc.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.
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).