Mercurial > emacs
comparison doc/misc/pgg.texi @ 85712:a3c27999decb
Update Gnus to No Gnus 0.7 from the Gnus CVS trunk
Revision: emacs@sv.gnu.org/emacs--devo--0--patch-911
author | Miles Bader <miles@gnu.org> |
---|---|
date | Sun, 28 Oct 2007 09:18:39 +0000 |
parents | 3d431f1997d8 |
children | 5d58981e6690 |
comparison
equal
deleted
inserted
replaced
85711:b6f5dc84b2e1 | 85712:a3c27999decb |
---|---|
343 singleton object wrapped with the luna object system. | 343 singleton object wrapped with the luna object system. |
344 | 344 |
345 Since PGG was designed for accessing and developing PGP functionality, | 345 Since PGG was designed for accessing and developing PGP functionality, |
346 the architecture had to be designed not just for interoperability but | 346 the architecture had to be designed not just for interoperability but |
347 also for extensiblity. In this chapter we explore the architecture | 347 also for extensiblity. In this chapter we explore the architecture |
348 while finding out how to write the PGG backend. | 348 while finding out how to write the PGG back end. |
349 | 349 |
350 @menu | 350 @menu |
351 * Initializing:: | 351 * Initializing:: |
352 * Backend methods:: | 352 * Back end methods:: |
353 * Getting output:: | 353 * Getting output:: |
354 @end menu | 354 @end menu |
355 | 355 |
356 @node Initializing | 356 @node Initializing |
357 @section Initializing | 357 @section Initializing |
371 (setq pgg-scheme-gpg-instance | 371 (setq pgg-scheme-gpg-instance |
372 (luna-make-entity 'pgg-scheme-gpg)))) | 372 (luna-make-entity 'pgg-scheme-gpg)))) |
373 @end lisp | 373 @end lisp |
374 | 374 |
375 The name of the function must follow the | 375 The name of the function must follow the |
376 regulation---@code{pgg-make-scheme-} follows the backend name. | 376 regulation---@code{pgg-make-scheme-} follows the back end name. |
377 | 377 |
378 @node Backend methods | 378 @node Back end methods |
379 @section Backend methods | 379 @section Back end methods |
380 | 380 |
381 In each backend, these methods must be present. The output of these | 381 In each back end, these methods must be present. The output of these |
382 methods is stored in special buffers (@ref{Getting output}), so that | 382 methods is stored in special buffers (@ref{Getting output}), so that |
383 these methods must tell the status of the execution. | 383 these methods must tell the status of the execution. |
384 | 384 |
385 @deffn Method pgg-scheme-lookup-key scheme string &optional type | 385 @deffn Method pgg-scheme-lookup-key scheme string &optional type |
386 Return keys associated with @var{string}. If the optional third | 386 Return keys associated with @var{string}. If the optional third |
433 @end deffn | 433 @end deffn |
434 | 434 |
435 @node Getting output | 435 @node Getting output |
436 @section Getting output | 436 @section Getting output |
437 | 437 |
438 The output of the backend methods (@ref{Backend methods}) is stored in | 438 The output of the back end methods (@ref{Back end methods}) is stored in |
439 special buffers, so that these methods must tell the status of the | 439 special buffers, so that these methods must tell the status of the |
440 execution. | 440 execution. |
441 | 441 |
442 @defvar pgg-errors-buffer | 442 @defvar pgg-errors-buffer |
443 The standard error output of the execution of the PGP command is stored | 443 The standard error output of the execution of the PGP command is stored |