Mercurial > emacs
view lisp/eshell/em-banner.el @ 111983:a348c631aeb8
- replace pgg with epg/epa - working version, with no calls to pgg.
- remove passphrase verifier and hinting.
(allout-passphrase-verifier-handling), (allout-passphrase-hint-handling):
No longer used, delete.
(allout-epg-protocol): Never used and unnecessary, delete.
(allout-mode): Adjust docstring to describe changed encryption provisions.
(allout-toggle-current-subtree-encryption): Adjust docstring to describe
changed encryption provisions. Change fetch-pass to keymode-cue, for
simpler universal argument interpretation.
(allout-toggle-subtree-encryption): Adjust docstring to describe
changed encryption provisions. Change fetch-pass to keymode-cue, for
simpler universal argument interpretation. Remove provisions for handling
key type and identity - they'll all be within allout-encrypt-string or
epg/epg or even contained all the way in gpg.
(allout-encrypt-string): Include keypair-mode argument, for requesting
keypair encryption. Require epa, for recipients handling. Change how
regexp filtering elements are named.
(allout-obtain-passphrase), (allout-epg-passphrase-callback-function),
(allout-make-passphrase-state), (allout-passphrase-state-passphrase):
Remove, we're not providing passphrase verification and hinting because:
- gpg v1 is required for epg passphrase callback operation, on which
verification and hinting depends
- doing that handling exposes the passphrase to emacs code, which is much
much less secure than leaving all passphrase handling in gpg
- leaving all passphrase handling to gpg removes a lot of complexity from
allout code
- gpg v2 connection to gpg-agent requires no user provisions, so is simpler
and provides some convenience that makes up for the lack of hinting and
verification
(allout-encrypted-key-info), (allout-update-passphrase-mnemonic-aids),
(allout-get-encryption-passphrase-verifier), (allout-verify-passphrase):
Obsolete.
author | Ken Manheimer <ken.manheimer@gmail.com> |
---|---|
date | Fri, 10 Dec 2010 17:09:57 -0500 |
parents | f57f72bb4757 |
children | 417b1e4d63cd |
line wrap: on
line source
;;; em-banner.el --- sample module that displays a login banner ;; Copyright (C) 1999, 2000, 2001, 2002, 2003, 2004, 2005, 2006, 2007, ;; 2008, 2009, 2010 Free Software Foundation, Inc. ;; Author: John Wiegley <johnw@gnu.org> ;; This file is part of GNU Emacs. ;; GNU Emacs is free software: you can redistribute it and/or modify ;; it under the terms of the GNU General Public License as published by ;; the Free Software Foundation, either version 3 of the License, or ;; (at your option) any later version. ;; GNU Emacs is distributed in the hope that it will be useful, ;; but WITHOUT ANY WARRANTY; without even the implied warranty of ;; MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the ;; GNU General Public License for more details. ;; You should have received a copy of the GNU General Public License ;; along with GNU Emacs. If not, see <http://www.gnu.org/licenses/>. ;;; Commentary: ;; There is nothing to be done or configured in order to use this ;; module, other than to select it by customizing the variable ;; `eshell-modules-list'. It will then display a version information ;; message whenever Eshell is loaded. ;; ;; This code is only an example of a how to write a well-formed ;; extension module for Eshell. The better way to display login text ;; is to use the `eshell-script' module, and to echo the desired ;; strings from the user's `eshell-login-script' file. ;; ;; There is one configuration variable, which demonstrates how to ;; properly define a customization variable in an extension module. ;; In this case, it allows the user to change the string which ;; displays at login time. ;;; Code: (eval-when-compile (require 'cl) (require 'esh-mode) (require 'eshell)) (require 'esh-util) ;;;###autoload (eshell-defgroup eshell-banner nil "This sample module displays a welcome banner at login. It exists so that others wishing to create their own Eshell extension modules may have a simple template to begin with." :tag "Login banner" ;; :link '(info-link "(eshell)Login banner") :group 'eshell-module) ;;; User Variables: (defcustom eshell-banner-message "Welcome to the Emacs shell\n\n" "The banner message to be displayed when Eshell is loaded. This can be any sexp, and should end with at least two newlines." :type 'sexp :group 'eshell-banner) (put 'eshell-banner-message 'risky-local-variable t) (defcustom eshell-banner-load-hook '(eshell-banner-initialize) "A list of functions to run when `eshell-banner' is loaded." :type 'hook :group 'eshell-banner) (defun eshell-banner-initialize () "Output a welcome banner on initialization." ;; it's important to use `eshell-interactive-print' rather than ;; `insert', because `insert' doesn't know how to interact with the ;; I/O code used by Eshell (unless eshell-non-interactive-p (assert eshell-mode) (assert eshell-banner-message) (let ((msg (eval eshell-banner-message))) (assert msg) (eshell-interactive-print msg)))) (eshell-deftest banner banner-displayed "Startup banner is displayed at point-min" (assert eshell-banner-message) (let ((msg (eval eshell-banner-message))) (assert msg) (goto-char (point-min)) (looking-at msg))) (provide 'em-banner) ;; Local Variables: ;; generated-autoload-file: "esh-groups.el" ;; End: ;; arch-tag: e738b4ef-8671-42ae-a757-291779b92491 ;;; em-banner.el ends here