Gnus development mailing list
 help / color / mirror / Atom feed
From: Kai.Grossjohann@CS.Uni-Dortmund.DE (Kai Großjohann)
Cc: ding@gnus.org
Subject: Re: Function definition wrong
Date: 13 Feb 2000 02:16:25 +0100	[thread overview]
Message-ID: <vafg0uxvr4m.fsf@lucy.cs.uni-dortmund.de> (raw)
In-Reply-To: Pieter Wenk's message of "Sat, 12 Feb 2000 17:10:01 +0100"

Pieter Wenk <pwenk@urbanet.ch> writes:

> Nos how can you under gnus without hassle arrange
> that messages are in accordance to the used langua-
> ges.
> 
> I.e. wrote
>       schrieb am 
> 
> I can't imagine, that under gnus this is  linked
> to some akward complicated commands.

Well, the current implementation of SC really requires you to write
functions.  However, this is quite easy to do by just copying and
pasting code from the old function.  Lessee.  Let's take
sc-header-author-writes as an example.  Here is the function
definition:

/----[ M-x find-function RET sc-header-author-writes RET ]
| (defun sc-header-author-writes ()
|   "<sc-author> writes:"
|   (let ((sc-mumble "")
|         (whofrom (sc-whofrom)))
|     (if whofrom
|         (insert sc-reference-tag-string
|                 (sc-hdr "" (sc-mail-field "sc-author"))
|                 " writes:\n"))))
\----

Even without understanding any of it, I'm sure you can quickly see how
to change the function name from sc-header-author-writes to
sc-header-author-schrieb, and how to change the `writes' to `schrieb'!
(One occurrence is the documentation...)

That's all there is to it.  Programming by copy and paste is a rather
simple thing.  No voodoo, no magic.

You can work your way up to more complex stuff later.

kai
-- 
~/.signature: No such file or directory



  reply	other threads:[~2000-02-13  1:16 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-02-11 16:25 Pieter Wenk
2000-02-11 17:28 ` Kai Großjohann
2000-02-12  7:28   ` Pieter Wenk
2000-02-12 12:41     ` Kai Großjohann
2000-02-12 16:10       ` Pieter Wenk
2000-02-13  1:16         ` Kai Großjohann [this message]
2000-02-13 10:36           ` Pieter Wenk
2000-02-13 13:22             ` Kai Großjohann
2000-02-14 14:29               ` Pieter Wenk
2000-02-14 15:18                 ` Kai Großjohann

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=vafg0uxvr4m.fsf@lucy.cs.uni-dortmund.de \
    --to=kai.grossjohann@cs.uni-dortmund.de \
    --cc=ding@gnus.org \
    /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).