unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: "Stephan Stahl" <stahl@eos.franken.de>
Cc: Kevin Rodgers <ihs_4664@yahoo.com>, emacs-devel@gnu.org
Subject: Re: ansi-color.el and comint.el
Date: Wed, 27 Apr 2005 00:12:30 +0200 (CEST)	[thread overview]
Message-ID: <46120.194.95.226.87.1114553550.squirrel@wwws.franken.de> (raw)
In-Reply-To: <200504261500.j3QF0KT22961@raven.dms.auburn.edu>

Luc Teirlinck said:

> Would autoloading comint-output-filter-functions not work?  But the
> same problem could happen to any hook whose defvar gives it a
> non-nil value.  So I guess that any defvar of such a type that is
> not in a preloaded file should be autoloaded,

Yes that would work too.  Using require might have been a nice example
for "check your dependencies".  Not very important.  So autoload seems
like the ideal solution since both files are part of emacs.

Kevin Rodgers said:

> Would it work if ansi-color-for-comint-mode-on added
> ansi-color-process-output to comint-output-filter-functions?  If so,
> should ansi-color-for-comint-mode-off remove it?

No, because this does not change the fact that comint.el may not be
loaded.

When ansi-color.el does that add-hook when comint.el is not already
loaded comint-output-filter-functions is set to
(ansi-color-process-output)

When comint.el is already loaded comint-output-filter-functions is set
to (ansi-color-process-output comint-postoutput-scroll-to-bottom
comint-watch-for-password-prompt)
-- 
Stephan Stahl

  reply	other threads:[~2005-04-26 22:12 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-04-26 13:26 ansi-color.el and comint.el Stephan Stahl
2005-04-26 15:00 ` Luc Teirlinck
2005-04-26 22:12   ` Stephan Stahl [this message]
2005-04-26 20:11 ` Kevin Rodgers

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=46120.194.95.226.87.1114553550.squirrel@wwws.franken.de \
    --to=stahl@eos.franken.de \
    --cc=emacs-devel@gnu.org \
    --cc=ihs_4664@yahoo.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.
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).