Gnus development mailing list
 help / color / mirror / Atom feed
From: Josh Huber <huber@alum.wpi.edu>
Subject: Re: `C-c C-v' should keep citation prefix
Date: 22 Jun 2001 10:14:33 -0400	[thread overview]
Message-ID: <878zikbnzq.fsf@mclinux.com> (raw)
In-Reply-To: <vafsngs96wm.fsf@lucy.cs.uni-dortmund.de>

Kai.Grossjohann@CS.Uni-Dortmund.DE (Kai Großjohann) writes:

> Are you sure you put it in .emacs and not .gnus?  Load-path frobbing
> can't be done from .gnus -- then parts of Gnus have already been
> loaded and it's too late.

It's definitely before gnus is loaded.

> And if something in .emacs causes parts of Gnus to be loaded, even
> somewhere low in .emacs it could be too late.

It's the first thing that's done in my initialization code.

> Just before frobbing load-path, you could have a look at the variable
> load-history to see if parts of Gnus have already been loaded.

This is a good idea :)

There are may parts of gnus loaded before I do anything in my init
code:

...
gnus-define-keys-safe gnus-define-keymap gnus-define-keys-1
gnus-completing-read gnus-y-or-n-p gnus-yes-or-no-p gnus-dd-mmm
gnus-date-get-time gnus-time-iso8601 gnus-date-iso8601
gnus-mode-string-quote gnus-make-hashtable gnus-create-hash-size
gnus-verbose gnus-message gnus-error gnus-split-references
gnus-parent-id gnus-buffer-live-p gnus-horizontal-recenter
gnus-read-event-char gnus-sortable-date gnus-copy-file
gnus-work-buffer gnus-set-work-buffer gnus-group-real-name
gnus-make-sort-function gnus-make-sort-function-1
gnus-turn-off-edit-menu gnus-prin1 gnus-prin1-to-string
gnus-make-directory gnus-write-buffer gnus-delete-file
gnus-strip-whitespace gnus-put-text-property-excluding-newlines
gnus-put-text-property-excluding-characters-with-faces
gnus-atomic-be-safe gnus-atomic-progn gnus-atomic-progn-assign
gnus-atomic-setq gnus-output-to-rmail gnus-output-to-mail
gnus-convert-article-to-rmail gnus-map-function gnus-run-hooks
gnus-parse-netrc gnus-netrc-machine gnus-netrc-get gnus-alive-p
gnus-remove-duplicates gnus-delete-if gnus-delete-alist gnus-pull
gnus-globalify-regexp gnus-set-window-start
...

hmmm...

I can just remove the gnus directory for the old version, but I really
would like to solve this the right way.  that way, the next time I
upgrade my xemacs packages, it doesn't copy a new (old) gnus directory
in /usr/share/xemacs21/packages/lisp/.

hmm!

-- 
Josh Huber


  reply	other threads:[~2001-06-22 14:14 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-06-02 19:50 Kai Großjohann
2001-06-05  0:06 ` Steven E. Harris
2001-06-05 18:37   ` Simon Josefsson
2001-06-05 23:54     ` Steven E. Harris
2001-06-19 19:42       ` Simon Josefsson
2001-06-20  2:07         ` Josh Huber
2001-06-20  8:22           ` Simon Josefsson
2001-06-20 13:03             ` Josh Huber
2001-06-20 13:12               ` Simon Josefsson
2001-06-20 13:21                 ` Josh Huber
2001-06-20 14:36                   ` David S. Goldberg
2001-06-22  9:54                   ` Kai Großjohann
2001-06-22 14:14                     ` Josh Huber [this message]
2001-06-22 15:45                       ` Paul Jarc
2001-06-22 19:02                         ` Josh Huber

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=878zikbnzq.fsf@mclinux.com \
    --to=huber@alum.wpi.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).