ChinStrap said:
Well I would be more than willing to learn Emacs if it does all these
things you speak of, but really I can't get started because the default
scheme is so friggin ugly it isn't funny.
Anyone want to send me a configuration setup with Python in mind, and
decent colors?
Set .emacs for:
;;; basic
(set-background-color "white")
(set-foreground-color "black")
(set-border-color "black")
(setq column-number-mode t)
(setq dired-ls-F-marks-symlinks t)
Do that prior to the python settings:
;---python---------------------------
(load "python-mode")
(setq auto-mode-alist
(cons '("\\.py$" . python-mode) auto-mode-alist))
(setq interpreter-mode-alist
(cons '("python" . python-mode)
interpreter-mode-alist))
(autoload 'python-mode "python-mode" "Python editing mode." t)
(add-hook 'python-mode-hook 'turn-on-font-lock)
(setq python-mode-hook 'python-initialise)
(defun python-initialise ()
(interactive)
(setq default-tab-width 4)
(setq indent-tabs-mode nil)
)
Then the default color scheme looks ok (at least to me).
The critical command is:
(add-hook 'python-mode-hook 'turn-on-font-lock)
If you comment that out (with a leading ";"), then font coloring is
turned off and you just have black on white. You can learn the
language and the editor in that mode if necessary.
--
(e-mail address removed)
6-6M21 BCA CompArch Design Engineering
Phone: (425) 294-4718
#! rnews 1727
Xref: xyzzy comp.security.ssh:39215
Newsgroups: comp.security.ssh
Path: xyzzy!nntp
From: "Mike Lowery" <
[email protected]>
Subject: Re: Ignoring known_hosts
X-Nntp-Posting-Host: e458612.nw.nos.boeing.com
Message-ID: <
[email protected]>
X-Mimeole: Produced By Microsoft MimeOLE V6.00.2800.1441
X-Priority: 3
X-Msmail-Priority: Normal
Lines: 33
Sender: (e-mail address removed) (Boeing NNTP News Access)
Organization: The Boeing Company
X-Newsreader: Microsoft Outlook Express 6.00.2800.1437
References: <
[email protected]> <
[email protected]> <
[email protected]> <
[email protected]>
Date: Wed, 6 Apr 2005 19:36:09 GMT
Richard E. Silverman said:
[~/.ssh/known_hosts]
foo [foo's key ...] bar [foo's key ...]
[~/.ssh/config]
host foo hostname <foo's name or address> hostkeyalias foo
host bar hostname <bar's name or address> hostkeyalias bar
... and use "ssh {foo|bar}".
Mike> This might work
It will work.
Mike> but again, it requires me manually adding each server to the
Mike> config file which I'm hoping to avoid since there are many.
How? If your machines are not uniquely identified to the client by their
names or addresses, then you must indicate the distinctions yourself by
configuration.
How? Tell SSH to stop checking for this potential "problem." I don't care that
the key doesn't match what it was last time, just give me access! Apparently
that option doesn't exist.