Gnus development mailing list
 help / color / mirror / Atom feed
From: Shenghuo ZHU <zsh@cs.rochester.edu>
Subject: Re: Group Customize
Date: 19 Sep 1998 23:47:28 -400	[thread overview]
Message-ID: <2ng1dnxx67.fsf@zsh.cs.rochester.edu> (raw)
In-Reply-To: Lars Magne Ingebrigtsen's message of "19 Sep 1998 14:29:26 +0200"

>>>>> "LMI" == Lars Magne Ingebrigtsen <larsi@gnus.org> writes:

LMI> Shenghuo ZHU <zsh@cs.rochester.edu> writes:
>> When gnus-group-customize, I edited it like the followings. When press
>> "G c" again, ERROR!  Did I do something wrong? Or it is a bug.
>> 
>> Variables:
>> Set variables local to the group you are entering. [More]
>> [INS]
>> 
>> Unknown entries:
>> [INS] [DEL] Lisp expression: (charset . cn-gb-2312)
>> [INS]

LMI> Hm.  Perhaps there's something the matter with the spec for some
LMI> variable?  Does `(setq debug-on-error t)' give you a backtrace?

LMI> -- 
LMI> (domestic pets only, the antidote for overdose, milk.)
LMI>   larsi@gnus.org * Lars Magne Ingebrigtsen

When I put varialbe charset and value cn-gb-2312 in the *Variables*
section, it is equivalent to (charset cn-gb-2312) in *Unknown
entries*, but it does not work. So I have to put 
(charset . cn-gb-2312) in the section.

The follows are the backtrace.  This bug appears in both emacs 20.3
and xemacs 20.4.

Signaling: (wrong-type-argument listp cn-gb-2312)
  widget-match-inline((sexp :value "nil" :tag "Value") cn-gb-2312)
  widget-group-match-inline((group :value (nil nil) :args ((symbol :value "nil" :tag "Variable") (sexp :value "nil" :tag "Value"))) (charset . cn-gb-2312))
  widget-group-match((group :value (nil nil) :args ((symbol :value "nil" :tag "Variable") (sexp :value "nil" :tag "Value"))) (charset . cn-gb-2312))
  widget-apply((group :value (nil nil) :args ((symbol :value "nil" :tag "Variable") (sexp :value "nil" :tag "Value"))) :match (charset . cn-gb-2312))
  widget-match-inline((group :value (nil nil) :args ((symbol :value "nil" :tag "Variable") (sexp :value "nil" :tag "Value"))) ((charset . cn-gb-2312)))
  widget-editable-list-match-inline((repeat :inline t :tag "Variables" :format "%t:\n%h%v%i\n\n" :doc "Set variables local to the group you are entering.\n\nIf you want to turn threading off in `news.answers', you could put\n`(gnus-show-threads nil)' in the group parameters of that group.\n`gnus-show-threads' will be made into a local variable in the summary\nbuffer you enter, and the form `nil' will be `eval'ed there.\n\nThis can also be used as a group-specific hook function, if you'd\nlike.  If you want to hear a beep when you enter a group, you could\nput something like `(dummy-variable (ding))' in the parameters of that\ngroup.  `dummy-variable' will be set to the result of the `(ding)'\nform, but who cares?" :args ((group :value ... :args ...))) ((charset . cn-gb-2312)))
  widget-apply((repeat :inline t :tag "Variables" :format "%t:\n%h%v%i\n\n" :doc "Set variables local to the group you are entering.\n\nIf you want to turn threading off in `news.answers', you could put\n`(gnus-show-threads nil)' in the group parameters of that group.\n`gnus-show-threads' will be made into a local variable in the summary\nbuffer you enter, and the form `nil' will be `eval'ed there.\n\nThis can also be used as a group-specific hook function, if you'd\nlike.  If you want to hear a beep when you enter a group, you could\nput something like `(dummy-variable (ding))' in the parameters of that\ngroup.  `dummy-variable' will be set to the result of the `(ding)'\nform, but who cares?" :args ((group :value ... :args ...))) :match-inline ((charset . cn-gb-2312)))
  widget-match-inline((repeat :inline t :tag "Variables" :format "%t:\n%h%v%i\n\n" :doc "Set variables local to the group you are entering.\n\nIf you want to turn threading off in `news.answers', you could put\n`(gnus-show-threads nil)' in the group parameters of that group.\n`gnus-show-threads' will be made into a local variable in the summary\nbuffer you enter, and the form `nil' will be `eval'ed there.\n\nThis can also be used as a group-specific hook function, if you'd\nlike.  If you want to hear a beep when you enter a group, you could\nput something like `(dummy-variable (ding))' in the parameters of that\ngroup.  `dummy-variable' will be set to the result of the `(ding)'\nform, but who cares?" :args ((group :value ... :args ...))) ((charset . cn-gb-2312)))
  widget-group-value-create((group :value ((charset . cn-gb-2312)) :args ((set :inline t :greedy t :tag "Parameters" :format "%t:\n%h%v" :doc "These special paramerters are recognized by Gnus.\nCheck the [ ] for the parameters you want to apply to this group, then\nedit the value to suit your taste." :args ...) (repeat :inline t :tag "Variables" :format "%t:\n%h%v%i\n\n" :doc "Set variables local to the group you are entering.\n\nIf you want to turn threading off in `news.answers', you could put\n`(gnus-show-threads nil)' in the group parameters of that group.\n`gnus-show-threads' will be made into a local variable in the summary\nbuffer you enter, and the form `nil' will be `eval'ed there.\n\nThis can also be used as a group-specific hook function, if you'd\nlike.  If you want to hear a beep when you enter a group, you could\nput something like `(dummy-variable (ding))' in the parameters of that\ngroup.  `dummy-variable' will be set to the result of the `(ding)'\nform, but !
 
 who cares?" :args ...) (repeat :inline t :tag "Unknown entries" :args ...))))
  widget-apply((group :value ((charset . cn-gb-2312)) :args ((set :inline t :greedy t :tag "Parameters" :format "%t:\n%h%v" :doc "These special paramerters are recognized by Gnus.\nCheck the [ ] for the parameters you want to apply to this group, then\nedit the value to suit your taste." :args ...) (repeat :inline t :tag "Variables" :format "%t:\n%h%v%i\n\n" :doc "Set variables local to the group you are entering.\n\nIf you want to turn threading off in `news.answers', you could put\n`(gnus-show-threads nil)' in the group parameters of that group.\n`gnus-show-threads' will be made into a local variable in the summary\nbuffer you enter, and the form `nil' will be `eval'ed there.\n\nThis can also be used as a group-specific hook function, if you'd\nlike.  If you want to hear a beep when you enter a group, you could\nput something like `(dummy-variable (ding))' in the parameters of that\ngroup.  `dummy-variable' will be set to the result of the `(ding)'\nform, but who cares?" :!
 
 args ...) (repeat :inline t :tag "Unknown entries" :args ...))) :value-create)
  widget-default-create((group :value ((charset . cn-gb-2312)) :args ((set :inline t :greedy t :tag "Parameters" :format "%t:\n%h%v" :doc "These special paramerters are recognized by Gnus.\nCheck the [ ] for the parameters you want to apply to this group, then\nedit the value to suit your taste." :args ...) (repeat :inline t :tag "Variables" :format "%t:\n%h%v%i\n\n" :doc "Set variables local to the group you are entering.\n\nIf you want to turn threading off in `news.answers', you could put\n`(gnus-show-threads nil)' in the group parameters of that group.\n`gnus-show-threads' will be made into a local variable in the summary\nbuffer you enter, and the form `nil' will be `eval'ed there.\n\nThis can also be used as a group-specific hook function, if you'd\nlike.  If you want to hear a beep when you enter a group, you could\nput something like `(dummy-variable (ding))' in the parameters of that\ngroup.  `dummy-variable' will be set to the result of the `(ding)'\nform, but who !
 
 cares?" :args ...) (repeat :inline t :tag "Unknown entries" :args ...))))
  widget-apply((group :value ((charset . cn-gb-2312)) :args ((set :inline t :greedy t :tag "Parameters" :format "%t:\n%h%v" :doc "These special paramerters are recognized by Gnus.\nCheck the [ ] for the parameters you want to apply to this group, then\nedit the value to suit your taste." :args ...) (repeat :inline t :tag "Variables" :format "%t:\n%h%v%i\n\n" :doc "Set variables local to the group you are entering.\n\nIf you want to turn threading off in `news.answers', you could put\n`(gnus-show-threads nil)' in the group parameters of that group.\n`gnus-show-threads' will be made into a local variable in the summary\nbuffer you enter, and the form `nil' will be `eval'ed there.\n\nThis can also be used as a group-specific hook function, if you'd\nlike.  If you want to hear a beep when you enter a group, you could\nput something like `(dummy-variable (ding))' in the parameters of that\ngroup.  `dummy-variable' will be set to the result of the `(ding)'\nform, but who cares?" :!
 
 args ...) (repeat :inline t :tag "Unknown entries" :args ...))) :create)
  widget-create(group :value ((charset . cn-gb-2312)) (set :inline t :greedy t :tag "Parameters" :format "%t:\n%h%v" :doc "These special paramerters are recognized by Gnus.\nCheck the [ ] for the parameters you want to apply to this group, then\nedit the value to suit your taste." (cons :format "%v%h\n" :doc "This will be used when doing followups and posts.\n\nThis is primarily useful in mail groups that represent closed\nmailing lists--mailing lists where it's expected that everybody that\nwrites to the mailing list is subscribed to it.  Since using this\nparameter ensures that the mail only goes to the mailing list itself,\nit means that members won't receive two copies of your followups.\n\nUsing `to-address' will actually work whether the group is foreign or\nnot.  Let's say there's a group on the server that is called\n`fa.4ad-l'.  This is a real newsgroup, but the server has gotten the\narticles from a mail-to-news gateway.  Posting directly to this group\nis therefor!
 
 e impossible--you have to send mail to the mailing list\naddress instead." (const :format "" to-address) (gnus-email-address :tag "To Address")) (cons :format "%v%h\n" :doc "This address will be used when doing a `a' in the group.\n\nIt is totally ignored when doing a followup--except that if it is\npresent in a news group, you'll get mail group semantics when doing\n`f'." (const :format "" to-list) (gnus-email-address :tag "To List")) (cons :format "%v%h\n" :doc "Ignore `Reply-To' headers in this group.\n\nThat can be useful if you're reading a mailing list group where the\nlistserv has inserted `Reply-To' headers that point back to the\nlistserv itself.  This is broken behavior.  So there!" (const :format "" broken-reply-to) (const :tag "Broken Reply To" t)) (cons :format "%v%h\n" :doc "All posts will be send to the specified group." (const :format "" to-group) (string :tag "To Group")) (cons :format "%v%h\n" :doc "Specify default value for GCC header.\n\nIf this symbol i!
 
 s present in the group parameter list and set to `t',\nnew compo!
sed messages will be `Gcc''d to the current group. If it is\npresent and set to `none', no `Gcc:' header will be generated, if it\nis present and a string, this string will be inserted literally as a\n`gcc' header (this symbol takes precedence over any default `Gcc'\nrules as described later)." (const :format "" gcc-self) (choice :tag "GCC" :value t ... ... ...)) (cons :format "%v%h\n" :doc "All articles that are read will be marked as expirable." (const :format "" auto-expire) (const :tag "Automatic Expire" t)) (cons :format "%v%h\n" :doc "All read articles will be put through the expiry process\n\nThis happens even if they are not marked as expirable.\nUse with caution." (const :format "" total-expire) (const :tag "Total Expire" t)) (cons :format "%v%h\n" :doc "When to expire.\n\nOverrides any `nnmail-expiry-wait' and `nnmail-expiry-wait-function'\nwhen expiring expirable messages. The value can either be a number of\ndays (not necessarily an integer) or the symbols `never!
 
 ' or\n`immediate'." (const :format "" expiry-wait) (choice :tag "Expire Wait" :value never ... ... ...)) (cons :format "%v%h\n" :doc "Make the specified file into the current score file.\nThis means that all score commands you issue will end up in this file." (const :format "" score-file) (file :tag "Score File")) (cons :format "%v%h\n" :doc "Make the specified file into the current adaptive file.\nAll adaptive score entries will be put into this file." (const :format "" adapt-file) (file :tag "Adapt File")) (cons :format "%v%h\n" :doc "Administration address for a mailing list.\n\nWhen unsubscribing to a mailing list you should never send the\nunsubscription notice to the mailing list itself.  Instead, you'd\nsend messages to the administrative address.  This parameter allows\nyou to put the admin address somewhere convenient." (const :format "" admin-address) (gnus-email-address :tag "Admin Address")) (cons :format "%v%h\n" :doc "Which articles to display on entering the !
 
 group.\n\n`all'\n     Display all articles, both read and unread!
.\n\n`default'\n     Display the default visible articles, which normally includes\n     unread and ticked articles." (const :format "" display) (choice :tag "Display" :value default ... ...)) (cons :format "%v%h\n" :doc "An arbitrary comment on the group." (const :format "" comment) (string :tag "Comment")) (cons :format "%v%h\n" :doc "Always display this group, even when there are no unread articles\nin it.." (const :format "" visible) (const :tag "Permanently visible" t))) (repeat :inline t :tag "Variables" :format "%t:\n%h%v%i\n\n" :doc "Set variables local to the group you are entering.\n\nIf you want to turn threading off in `news.answers', you could put\n`(gnus-show-threads nil)' in the group parameters of that group.\n`gnus-show-threads' will be made into a local variable in the summary\nbuffer you enter, and the form `nil' will be `eval'ed there.\n\nThis can also be used as a group-specific hook function, if you'd\nlike.  If you want to hear a beep when you enter a !
 
 group, you could\nput something like `(dummy-variable (ding))' in the parameters of that\ngroup.  `dummy-variable' will be set to the result of the `(ding)'\nform, but who cares?" (group :value (nil nil) (symbol :tag "Variable") (sexp :tag "Value"))) (repeat :inline t :tag "Unknown entries" sexp))
  #<compiled-function (from "gnus-cus.elc") (group) "...(278)" [nil mapcar #<compiled-function (from "gnus-cus.elc") ... "...(29)" ... 9> gnus-group-parameters types info group error "No group on current line" 2 intern-soft gnus-newsrc-hashtb "Killed group; can't be edited" kill-buffer gnus-get-buffer-create "*Gnus Customize*" switch-to-buffer gnus-custom-mode make-local-variable gnus-custom-group widget-insert "Customize the " widget-create info-link :help-echo "Push me to learn more." :tag "group parameters" "(gnus)Group Parameters" " for <" "> and press " push-button "done" "Push me when done customizing." :action gnus-group-customize-done ".\n\n" gnus-custom-params :value 5 set :inline t :greedy "Parameters" :format "%t:\n%h%v" :doc "These special paramerters are recognized by Gnus.\nCheck the [ ] for the parameters you want to apply to this group, then\nedit the value to suit your taste." (repeat :inline t :tag "Variables" :format "%t:\n%h%v%i\n\n" :doc "Set variables l!
 
 ocal to the group you are entering.\n\nIf you want to turn threading off in `news.answers', you could put\n`(gnus-show-threads nil)' in the group parameters of that group.\n`gnus-show-threads' will be made into a local variable in the summary\nbuffer you enter, and the form `nil' will be `eval'ed there.\n\nThis can also be used as a group-specific hook function, if you'd\nlike.  If you want to hear a beep when you enter a group, you could\nput something like `(dummy-variable (ding))' in the parameters of that\ngroup.  `dummy-variable' will be set to the result of the `(ding)'\nform, but who cares?" ...) ...] 16 ("/u/zsh/emacs/xemacs/gnus-cus.elc" . 5472) (list (gnus-group-group-name))>("nnml:test")
  call-interactively(gnus-group-customize)


-- 
Shenghuo


  reply	other threads:[~1998-09-20  3:47 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1998-09-17 20:03 Shenghuo ZHU
1998-09-19 12:29 ` Lars Magne Ingebrigtsen
1998-09-20  3:47   ` Shenghuo ZHU [this message]
1998-09-23 19:50     ` Lars Magne Ingebrigtsen
1998-09-24  6:12       ` Shenghuo ZHU

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=2ng1dnxx67.fsf@zsh.cs.rochester.edu \
    --to=zsh@cs.rochester.edu \
    /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).