remember 39 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168169170171172173174175176177178179180181182183184185186187188189190191192193194195196197198199200201202203204205206207208209210211212213214215216217218219220221222223224225226227228229230231232233234235236237238239240241242243244245246247248249250251252253254255256257258259260261262263264265266267268269270271272273274275276277278279280281282283284285286287288289290291292293294295296297298299300301302303304305306307308309310311312313314315316317318319320321322323324325326327328329330331332333334335336337338339340341342343344345346347348349350351352353354355356357358359360361362363364365366367368369370371372373374375376377378379380381382383384385386387388389390391392393394395396397398399400401402403404405406407408409410411412413414415416417418419420421422423424425426427428429430431432433434435436437438439440441442443444445446447448449450451452453454455456457458459460461462463464465466467468469470471472473474475476477478479480481482483484485486487488489490491492493494495496497498499500501502503504505506507508509510511512513514515516517518519520521522523524525526527528529530531532533534535536537538539540541542543544545546547548549550551552553554555556557558559560561562563564565566567568569570571572573574575576577578579580581582583584585586587588589590591592593594595596597598599600601602603604605606607608609610611612613614615616617618619620621622623624625626627628629630631632633634635636637638639640641642643644645646647648649650651652653654655656657658659660661662663664665666667668669670671672673674675676677678679680681682683684685686687688689690691692693694695696697698699700701702703704705706707708709710711712713714715716717718719720721722723724725726727728729730731732733734735736737738739740741742743744745746747748749750751752753754755756757758759760761762763764765766767768769770771772773774775776777778779780781782783784785786787788789790791792793794795796797798799800801802803804805806807808809810811812813814815816817818819820821822823824825826827828829830831832833834835836837838839840841842843844845846847848849850851852853854855856857858859860861862863864865866867868869870871872873874875876877878879880881882883884885886887888889890891892893894895896897898899900901902903904
  1. This is ../../info/remember, produced by makeinfo version 4.13 from
  2. remember.texi.
  3. This manual is for Remember Mode, version 1.9
  4. Copyright (C) 2001, 2004-2005, 2007-2012 Free Software Foundation,
  5. Inc.
  6. Permission is granted to copy, distribute and/or modify this
  7. document under the terms of the GNU Free Documentation License,
  8. Version 1.3 or any later version published by the Free Software
  9. Foundation; with no Invariant Sections, with the Front-Cover texts
  10. being "A GNU Manual", and with the Back-Cover Texts as in (a)
  11. below. A copy of the license is included in the section entitled
  12. "GNU Free Documentation License".
  13. (a) The FSF's Back-Cover Text is: "You have the freedom to copy and
  14. modify this GNU manual. Buying copies from the FSF supports it in
  15. developing GNU and promoting software freedom."
  16. INFO-DIR-SECTION Emacs misc features
  17. START-INFO-DIR-ENTRY
  18. * Remember: (remember). Simple information manager for Emacs.
  19. END-INFO-DIR-ENTRY
  20. 
  21. File: remember, Node: Top, Next: Preface, Prev: (dir), Up: (dir)
  22. Remember
  23. ********
  24. This manual is for Remember Mode, version 1.9
  25. Copyright (C) 2001, 2004-2005, 2007-2012 Free Software Foundation,
  26. Inc.
  27. Permission is granted to copy, distribute and/or modify this
  28. document under the terms of the GNU Free Documentation License,
  29. Version 1.3 or any later version published by the Free Software
  30. Foundation; with no Invariant Sections, with the Front-Cover texts
  31. being "A GNU Manual", and with the Back-Cover Texts as in (a)
  32. below. A copy of the license is included in the section entitled
  33. "GNU Free Documentation License".
  34. (a) The FSF's Back-Cover Text is: "You have the freedom to copy and
  35. modify this GNU manual. Buying copies from the FSF supports it in
  36. developing GNU and promoting software freedom."
  37. * Menu:
  38. * Preface:: About the documentation.
  39. * Introduction:: What is Remember Mode?
  40. * Installation:: How to install Remember.
  41. * Implementation:: How Remember came into existence.
  42. * Quick Start:: Get started using Remember.
  43. * Function Reference:: Interactive functions in remember.el.
  44. * Keystrokes:: Keystrokes bound in Remember Mode.
  45. * Backends:: Backends for saving notes.
  46. * GNU Free Documentation License:: The license for this documentation.
  47. * Concept Index:: Search for terms.
  48. --- The Detailed Node Listing ---
  49. Backends
  50. * Text File:: Saving to a text file.
  51. * Diary:: Saving to a Diary file.
  52. * Mailbox:: Saving to a mailbox.
  53. * Org:: Saving to an Org Mode file.
  54. 
  55. File: remember, Node: Preface, Next: Introduction, Prev: Top, Up: Top
  56. 1 Preface
  57. *********
  58. This document describes remember-el, which was written by John Wiegley,
  59. was once maintained by Sacha Chua, and is now maintained by the Emacs
  60. developers.
  61. This document is a work in progress, and your contribution will be
  62. greatly appreciated.
  63. 
  64. File: remember, Node: Introduction, Next: Installation, Prev: Preface, Up: Top
  65. 2 Introduction
  66. **************
  67. Todo lists, schedules, phone databases... everything we use databases
  68. for is really just a way to extend the power of our memory, to be able
  69. to remember what our conscious mind may not currently have access to.
  70. There are many different databases out there--and good ones--which
  71. this mode is not trying to replace. Rather, it's how that data gets
  72. there that's the question. Most of the time, we just want to say
  73. "Remember so-and-so's phone number, or that I have to buy dinner for the
  74. cats tonight." That's the FACT. How it's stored is really the
  75. computer's problem. But at this point in time, it's most definitely
  76. also the user's problem, and sometimes so laboriously so that people
  77. just let data slip, rather than expend the effort to record it.
  78. "Remember" is a mode for remembering data. It uses whatever
  79. back-end is appropriate to record and correlate the data, but its main
  80. intention is to allow you to express as _little_ structure as possible
  81. up front. If you later want to express more powerful relationships
  82. between your data, or state assumptions that were at first too implicit
  83. to be recognized, you can "study" the data later and rearrange it. But
  84. the initial "just remember this" impulse should be as close to simply
  85. throwing the data at Emacs as possible.
  86. Have you ever noticed that having a laptop to write on doesn't
  87. _actually_ increase the amount of quality material that you turn out,
  88. in the long run? Perhaps it's because the time we save electronically
  89. in one way, we're losing electronically in another; the tool should
  90. never dominate one's focus. As the mystic Faridu'd-Din `Attar wrote:
  91. "Be occupied as little as possible with things of the outer world but
  92. much with things of the inner world; then right action will overcome
  93. inaction."
  94. If Emacs could become a more intelligent data store, where
  95. brainstorming would focus on the _ideas_ involved--rather than the
  96. structuring and format of those ideas, or having to stop your current
  97. flow of work in order to record them--it would map much more closely to
  98. how the mind (well, at least mine) works, and hence would eliminate
  99. that very manual-ness which computers from the very beginning have been
  100. championed as being able to reduce.
  101. 
  102. File: remember, Node: Installation, Next: Implementation, Prev: Introduction, Up: Top
  103. 3 Installation
  104. **************
  105. Installing Remember Mode is as simple as adding the following lines to
  106. your Emacs configuration file (usually `~/.emacs.d/init.el' or
  107. `~/.emacs').
  108. (add-to-list 'load-path "/path/to/remember")
  109. (require 'remember)
  110. 
  111. File: remember, Node: Implementation, Next: Quick Start, Prev: Installation, Up: Top
  112. 4 Implementation
  113. ****************
  114. Hyperbole, as a data presentation tool, always struck me as being very
  115. powerful, but it seemed to require a lot of "front-end" work before
  116. that data was really available. The problem with BBDB, or keeping up a
  117. Bibl-mode file, is that you have to use different functions to record
  118. the data, and it always takes time to stop what you're doing, format
  119. the data in the manner expected by that particular data interface, and
  120. then resume your work.
  121. With "remember", you just hit `M-x remember' (you'd probably want to
  122. bind this to an easily accessible keystroke, like `C-x M-r'), slam in
  123. your text however you like, and then hit `C-c C-c'. It will file the
  124. data away for later retrieval, and possibly indexing.
  125. Indexing is to data what "studying" is in the real world. What you
  126. do when you study (or lucubrate, for some of us) is to realize certain
  127. relationships implicit in the data, so that you can make use of those
  128. relationships. Expressing that a certain quote you remembered was a
  129. literary quote, and that you want the ability to pull up all quotes of a
  130. literary nature, is what studying does. This is a more labor intensive
  131. task than the original remembering of the data, and it's typical in real
  132. life to set aside a special period of time for doing this work.
  133. "Remember" works in the same way. When you enter data, either by
  134. typing it into a buffer, or using the contents of the selected region,
  135. it will store that data--unindexed, uninterpreted--in a data pool. It
  136. will also try to remember as much context information as possible (any
  137. text properties that were set, where you copied it from, when, how,
  138. etc). Later, you can walk through your accumulated set of data (both
  139. organized, and unorganized) and easily begin moving things around, and
  140. making annotations that will express the full meaning of that data, as
  141. far as you know it.
  142. Obviously this latter stage is more user-interface intensive, and it
  143. would be nice if "remember" could do it as elegantly as possible,
  144. rather than requiring a billion keystrokes to reorganize your
  145. hierarchy. Well, as the future arrives, hopefully experience and user
  146. feedback will help to make this as intuitive a tool as possible.
  147. 
  148. File: remember, Node: Quick Start, Next: Function Reference, Prev: Implementation, Up: Top
  149. 5 Quick Start
  150. *************
  151. * Load `remember.el'.
  152. * Type `M-x remember'. The `*Remember*' buffer should be displayed.
  153. * Type in what you want to remember. The first line will be treated
  154. as the headline, and the rest of the buffer will contain the body
  155. of the note.
  156. * Type `C-c C-c' (`remember-finalize') to save the note and close
  157. the `*Remember*' buffer.
  158. By default, `remember-finalize' saves the note in `~/.notes'. You
  159. can edit it now to see the remembered and timestamped note. You can
  160. edit this file however you want. New entries will always be added to
  161. the end.
  162. To remember a region of text, use the universal prefix. `C-u M-x
  163. remember' displays a `*Remember*' buffer with the region as the initial
  164. contents.
  165. As a simple beginning, you can start by using the Text File backend,
  166. keeping your `~/.notes' file in outline-mode format, with a final entry
  167. called `* Raw data'. Remembered data will be added to the end of the
  168. file. Every so often, you can move the data that gets appended there
  169. into other files, or reorganize your document.
  170. You can also store remembered data in other backends. (*note
  171. Backends::)
  172. Here is one way to map the remember functions in your `.emacs' to
  173. very accessible keystrokes facilities using the mode:
  174. (autoload 'remember ``remember'' nil t)
  175. (autoload 'remember-region ``remember'' nil t)
  176. (define-key global-map (kbd "<f9> r") 'remember)
  177. (define-key global-map (kbd "<f9> R") 'remember-region)
  178. By default, remember uses the first annotation returned by
  179. `remember-annotation-functions'. To include all of the annotations, set
  180. `remember-run-all-annotation-functions-flag' to non-nil.
  181. -- User Option: remember-run-all-annotation-functions-flag
  182. Non-nil means use all annotations returned by
  183. `remember-annotation-functions'.
  184. You can write custom functions that use a different set of
  185. remember-annotation-functions. For example:
  186. (defun my/remember-with-filename ()
  187. "Always use the filename."
  188. (interactive)
  189. (let ((remember-annotation-functions '(buffer-file-name)))
  190. (call-interactively 'remember)))
  191. 
  192. File: remember, Node: Function Reference, Next: Keystrokes, Prev: Quick Start, Up: Top
  193. 6 Function Reference
  194. ********************
  195. `remember.el' defines the following interactive functions:
  196. -- Function: remember initial
  197. Remember an arbitrary piece of data. With a prefix, it will use the
  198. region as INITIAL.
  199. -- Function: remember-region beg end
  200. If called from within the remember buffer, BEG and END are
  201. ignored, and the entire buffer will be remembered. If called from
  202. any other buffer, that region, plus any context information
  203. specific to that region, will be remembered.
  204. -- Function: remember-clipboard
  205. Remember the contents of the current clipboard. This is most
  206. useful for remembering things from Netscape or other X Windows
  207. applications.
  208. -- Function: remember-finalize
  209. Remember the contents of the current buffer.
  210. -- Function: remember-mode
  211. This enters the major mode for output from `remember'. This
  212. buffer is used to collect data that you want remember. Just hit
  213. `C-c C-c' when you're done entering, and it will go ahead and file
  214. the data for latter retrieval, and possible indexing.
  215. 
  216. File: remember, Node: Keystrokes, Next: Backends, Prev: Function Reference, Up: Top
  217. 7 Keystroke Reference
  218. *********************
  219. `remember.el' defines the following keybindings by default:
  220. `C-c C-c (`remember-finalize')'
  221. Remember the contents of the current buffer.
  222. `C-c C-k (`remember-destroy')'
  223. Destroy the current *Remember* buffer.
  224. `C-x C-s (`remember-finalize')'
  225. Remember the contents of the current buffer.
  226. 
  227. File: remember, Node: Backends, Next: GNU Free Documentation License, Prev: Keystrokes, Up: Top
  228. 8 Backends
  229. **********
  230. You can save remembered notes to a variety of backends.
  231. * Menu:
  232. * Text File:: Saving to a text file.
  233. * Diary:: Saving to a Diary file.
  234. * Mailbox:: Saving to a mailbox.
  235. * Org:: Saving to an Org Mode file.
  236. 
  237. File: remember, Node: Text File, Next: Diary, Prev: Backends, Up: Backends
  238. 8.1 Saving to a Text File
  239. =========================
  240. Insinuation
  241. -----------
  242. (setq remember-handler-functions '(remember-append-to-file))
  243. Options
  244. -------
  245. -- User Option: remember-data-file
  246. The file in which to store unprocessed data.
  247. -- User Option: remember-leader-text
  248. The text used to begin each remember item.
  249. 
  250. File: remember, Node: Diary, Next: Mailbox, Prev: Text File, Up: Backends
  251. 8.2 Saving to a Diary file
  252. ==========================
  253. Insinuation
  254. -----------
  255. (add-to-list 'remember-handler-functions 'remember-diary-extract-entries)
  256. Options
  257. -------
  258. -- User Option: remember-diary-file
  259. File for extracted diary entries. If this is nil, then
  260. `diary-file' will be used instead."
  261. 
  262. File: remember, Node: Mailbox, Next: Org, Prev: Diary, Up: Backends
  263. 8.3 Saving to a Mailbox
  264. =======================
  265. Insinuation
  266. -----------
  267. (add-to-list 'remember-handler-functions 'remember-store-in-mailbox)
  268. Options
  269. -------
  270. -- User Option: remember-mailbox
  271. The file in which to store remember data as mail.
  272. -- User Option: remember-default-priority
  273. The default priority for remembered mail messages.
  274. 
  275. File: remember, Node: Org, Prev: Mailbox, Up: Backends
  276. 8.4 Saving to an Org Mode file
  277. ==============================
  278. For instructions on how to integrate Remember with Org Mode, consult
  279. *note Capture: (org)Capture.
  280. 
  281. File: remember, Node: GNU Free Documentation License, Next: Concept Index, Prev: Backends, Up: Top
  282. Appendix A GNU Free Documentation License
  283. *****************************************
  284. Version 1.3, 3 November 2008
  285. Copyright (C) 2000, 2001, 2002, 2007, 2008, 2009 Free Software Foundation, Inc.
  286. `http://fsf.org/'
  287. Everyone is permitted to copy and distribute verbatim copies
  288. of this license document, but changing it is not allowed.
  289. 0. PREAMBLE
  290. The purpose of this License is to make a manual, textbook, or other
  291. functional and useful document "free" in the sense of freedom: to
  292. assure everyone the effective freedom to copy and redistribute it,
  293. with or without modifying it, either commercially or
  294. noncommercially. Secondarily, this License preserves for the
  295. author and publisher a way to get credit for their work, while not
  296. being considered responsible for modifications made by others.
  297. This License is a kind of "copyleft", which means that derivative
  298. works of the document must themselves be free in the same sense.
  299. It complements the GNU General Public License, which is a copyleft
  300. license designed for free software.
  301. We have designed this License in order to use it for manuals for
  302. free software, because free software needs free documentation: a
  303. free program should come with manuals providing the same freedoms
  304. that the software does. But this License is not limited to
  305. software manuals; it can be used for any textual work, regardless
  306. of subject matter or whether it is published as a printed book.
  307. We recommend this License principally for works whose purpose is
  308. instruction or reference.
  309. 1. APPLICABILITY AND DEFINITIONS
  310. This License applies to any manual or other work, in any medium,
  311. that contains a notice placed by the copyright holder saying it
  312. can be distributed under the terms of this License. Such a notice
  313. grants a world-wide, royalty-free license, unlimited in duration,
  314. to use that work under the conditions stated herein. The
  315. "Document", below, refers to any such manual or work. Any member
  316. of the public is a licensee, and is addressed as "you". You
  317. accept the license if you copy, modify or distribute the work in a
  318. way requiring permission under copyright law.
  319. A "Modified Version" of the Document means any work containing the
  320. Document or a portion of it, either copied verbatim, or with
  321. modifications and/or translated into another language.
  322. A "Secondary Section" is a named appendix or a front-matter section
  323. of the Document that deals exclusively with the relationship of the
  324. publishers or authors of the Document to the Document's overall
  325. subject (or to related matters) and contains nothing that could
  326. fall directly within that overall subject. (Thus, if the Document
  327. is in part a textbook of mathematics, a Secondary Section may not
  328. explain any mathematics.) The relationship could be a matter of
  329. historical connection with the subject or with related matters, or
  330. of legal, commercial, philosophical, ethical or political position
  331. regarding them.
  332. The "Invariant Sections" are certain Secondary Sections whose
  333. titles are designated, as being those of Invariant Sections, in
  334. the notice that says that the Document is released under this
  335. License. If a section does not fit the above definition of
  336. Secondary then it is not allowed to be designated as Invariant.
  337. The Document may contain zero Invariant Sections. If the Document
  338. does not identify any Invariant Sections then there are none.
  339. The "Cover Texts" are certain short passages of text that are
  340. listed, as Front-Cover Texts or Back-Cover Texts, in the notice
  341. that says that the Document is released under this License. A
  342. Front-Cover Text may be at most 5 words, and a Back-Cover Text may
  343. be at most 25 words.
  344. A "Transparent" copy of the Document means a machine-readable copy,
  345. represented in a format whose specification is available to the
  346. general public, that is suitable for revising the document
  347. straightforwardly with generic text editors or (for images
  348. composed of pixels) generic paint programs or (for drawings) some
  349. widely available drawing editor, and that is suitable for input to
  350. text formatters or for automatic translation to a variety of
  351. formats suitable for input to text formatters. A copy made in an
  352. otherwise Transparent file format whose markup, or absence of
  353. markup, has been arranged to thwart or discourage subsequent
  354. modification by readers is not Transparent. An image format is
  355. not Transparent if used for any substantial amount of text. A
  356. copy that is not "Transparent" is called "Opaque".
  357. Examples of suitable formats for Transparent copies include plain
  358. ASCII without markup, Texinfo input format, LaTeX input format,
  359. SGML or XML using a publicly available DTD, and
  360. standard-conforming simple HTML, PostScript or PDF designed for
  361. human modification. Examples of transparent image formats include
  362. PNG, XCF and JPG. Opaque formats include proprietary formats that
  363. can be read and edited only by proprietary word processors, SGML or
  364. XML for which the DTD and/or processing tools are not generally
  365. available, and the machine-generated HTML, PostScript or PDF
  366. produced by some word processors for output purposes only.
  367. The "Title Page" means, for a printed book, the title page itself,
  368. plus such following pages as are needed to hold, legibly, the
  369. material this License requires to appear in the title page. For
  370. works in formats which do not have any title page as such, "Title
  371. Page" means the text near the most prominent appearance of the
  372. work's title, preceding the beginning of the body of the text.
  373. The "publisher" means any person or entity that distributes copies
  374. of the Document to the public.
  375. A section "Entitled XYZ" means a named subunit of the Document
  376. whose title either is precisely XYZ or contains XYZ in parentheses
  377. following text that translates XYZ in another language. (Here XYZ
  378. stands for a specific section name mentioned below, such as
  379. "Acknowledgements", "Dedications", "Endorsements", or "History".)
  380. To "Preserve the Title" of such a section when you modify the
  381. Document means that it remains a section "Entitled XYZ" according
  382. to this definition.
  383. The Document may include Warranty Disclaimers next to the notice
  384. which states that this License applies to the Document. These
  385. Warranty Disclaimers are considered to be included by reference in
  386. this License, but only as regards disclaiming warranties: any other
  387. implication that these Warranty Disclaimers may have is void and
  388. has no effect on the meaning of this License.
  389. 2. VERBATIM COPYING
  390. You may copy and distribute the Document in any medium, either
  391. commercially or noncommercially, provided that this License, the
  392. copyright notices, and the license notice saying this License
  393. applies to the Document are reproduced in all copies, and that you
  394. add no other conditions whatsoever to those of this License. You
  395. may not use technical measures to obstruct or control the reading
  396. or further copying of the copies you make or distribute. However,
  397. you may accept compensation in exchange for copies. If you
  398. distribute a large enough number of copies you must also follow
  399. the conditions in section 3.
  400. You may also lend copies, under the same conditions stated above,
  401. and you may publicly display copies.
  402. 3. COPYING IN QUANTITY
  403. If you publish printed copies (or copies in media that commonly
  404. have printed covers) of the Document, numbering more than 100, and
  405. the Document's license notice requires Cover Texts, you must
  406. enclose the copies in covers that carry, clearly and legibly, all
  407. these Cover Texts: Front-Cover Texts on the front cover, and
  408. Back-Cover Texts on the back cover. Both covers must also clearly
  409. and legibly identify you as the publisher of these copies. The
  410. front cover must present the full title with all words of the
  411. title equally prominent and visible. You may add other material
  412. on the covers in addition. Copying with changes limited to the
  413. covers, as long as they preserve the title of the Document and
  414. satisfy these conditions, can be treated as verbatim copying in
  415. other respects.
  416. If the required texts for either cover are too voluminous to fit
  417. legibly, you should put the first ones listed (as many as fit
  418. reasonably) on the actual cover, and continue the rest onto
  419. adjacent pages.
  420. If you publish or distribute Opaque copies of the Document
  421. numbering more than 100, you must either include a
  422. machine-readable Transparent copy along with each Opaque copy, or
  423. state in or with each Opaque copy a computer-network location from
  424. which the general network-using public has access to download
  425. using public-standard network protocols a complete Transparent
  426. copy of the Document, free of added material. If you use the
  427. latter option, you must take reasonably prudent steps, when you
  428. begin distribution of Opaque copies in quantity, to ensure that
  429. this Transparent copy will remain thus accessible at the stated
  430. location until at least one year after the last time you
  431. distribute an Opaque copy (directly or through your agents or
  432. retailers) of that edition to the public.
  433. It is requested, but not required, that you contact the authors of
  434. the Document well before redistributing any large number of
  435. copies, to give them a chance to provide you with an updated
  436. version of the Document.
  437. 4. MODIFICATIONS
  438. You may copy and distribute a Modified Version of the Document
  439. under the conditions of sections 2 and 3 above, provided that you
  440. release the Modified Version under precisely this License, with
  441. the Modified Version filling the role of the Document, thus
  442. licensing distribution and modification of the Modified Version to
  443. whoever possesses a copy of it. In addition, you must do these
  444. things in the Modified Version:
  445. A. Use in the Title Page (and on the covers, if any) a title
  446. distinct from that of the Document, and from those of
  447. previous versions (which should, if there were any, be listed
  448. in the History section of the Document). You may use the
  449. same title as a previous version if the original publisher of
  450. that version gives permission.
  451. B. List on the Title Page, as authors, one or more persons or
  452. entities responsible for authorship of the modifications in
  453. the Modified Version, together with at least five of the
  454. principal authors of the Document (all of its principal
  455. authors, if it has fewer than five), unless they release you
  456. from this requirement.
  457. C. State on the Title page the name of the publisher of the
  458. Modified Version, as the publisher.
  459. D. Preserve all the copyright notices of the Document.
  460. E. Add an appropriate copyright notice for your modifications
  461. adjacent to the other copyright notices.
  462. F. Include, immediately after the copyright notices, a license
  463. notice giving the public permission to use the Modified
  464. Version under the terms of this License, in the form shown in
  465. the Addendum below.
  466. G. Preserve in that license notice the full lists of Invariant
  467. Sections and required Cover Texts given in the Document's
  468. license notice.
  469. H. Include an unaltered copy of this License.
  470. I. Preserve the section Entitled "History", Preserve its Title,
  471. and add to it an item stating at least the title, year, new
  472. authors, and publisher of the Modified Version as given on
  473. the Title Page. If there is no section Entitled "History" in
  474. the Document, create one stating the title, year, authors,
  475. and publisher of the Document as given on its Title Page,
  476. then add an item describing the Modified Version as stated in
  477. the previous sentence.
  478. J. Preserve the network location, if any, given in the Document
  479. for public access to a Transparent copy of the Document, and
  480. likewise the network locations given in the Document for
  481. previous versions it was based on. These may be placed in
  482. the "History" section. You may omit a network location for a
  483. work that was published at least four years before the
  484. Document itself, or if the original publisher of the version
  485. it refers to gives permission.
  486. K. For any section Entitled "Acknowledgements" or "Dedications",
  487. Preserve the Title of the section, and preserve in the
  488. section all the substance and tone of each of the contributor
  489. acknowledgements and/or dedications given therein.
  490. L. Preserve all the Invariant Sections of the Document,
  491. unaltered in their text and in their titles. Section numbers
  492. or the equivalent are not considered part of the section
  493. titles.
  494. M. Delete any section Entitled "Endorsements". Such a section
  495. may not be included in the Modified Version.
  496. N. Do not retitle any existing section to be Entitled
  497. "Endorsements" or to conflict in title with any Invariant
  498. Section.
  499. O. Preserve any Warranty Disclaimers.
  500. If the Modified Version includes new front-matter sections or
  501. appendices that qualify as Secondary Sections and contain no
  502. material copied from the Document, you may at your option
  503. designate some or all of these sections as invariant. To do this,
  504. add their titles to the list of Invariant Sections in the Modified
  505. Version's license notice. These titles must be distinct from any
  506. other section titles.
  507. You may add a section Entitled "Endorsements", provided it contains
  508. nothing but endorsements of your Modified Version by various
  509. parties--for example, statements of peer review or that the text
  510. has been approved by an organization as the authoritative
  511. definition of a standard.
  512. You may add a passage of up to five words as a Front-Cover Text,
  513. and a passage of up to 25 words as a Back-Cover Text, to the end
  514. of the list of Cover Texts in the Modified Version. Only one
  515. passage of Front-Cover Text and one of Back-Cover Text may be
  516. added by (or through arrangements made by) any one entity. If the
  517. Document already includes a cover text for the same cover,
  518. previously added by you or by arrangement made by the same entity
  519. you are acting on behalf of, you may not add another; but you may
  520. replace the old one, on explicit permission from the previous
  521. publisher that added the old one.
  522. The author(s) and publisher(s) of the Document do not by this
  523. License give permission to use their names for publicity for or to
  524. assert or imply endorsement of any Modified Version.
  525. 5. COMBINING DOCUMENTS
  526. You may combine the Document with other documents released under
  527. this License, under the terms defined in section 4 above for
  528. modified versions, provided that you include in the combination
  529. all of the Invariant Sections of all of the original documents,
  530. unmodified, and list them all as Invariant Sections of your
  531. combined work in its license notice, and that you preserve all
  532. their Warranty Disclaimers.
  533. The combined work need only contain one copy of this License, and
  534. multiple identical Invariant Sections may be replaced with a single
  535. copy. If there are multiple Invariant Sections with the same name
  536. but different contents, make the title of each such section unique
  537. by adding at the end of it, in parentheses, the name of the
  538. original author or publisher of that section if known, or else a
  539. unique number. Make the same adjustment to the section titles in
  540. the list of Invariant Sections in the license notice of the
  541. combined work.
  542. In the combination, you must combine any sections Entitled
  543. "History" in the various original documents, forming one section
  544. Entitled "History"; likewise combine any sections Entitled
  545. "Acknowledgements", and any sections Entitled "Dedications". You
  546. must delete all sections Entitled "Endorsements."
  547. 6. COLLECTIONS OF DOCUMENTS
  548. You may make a collection consisting of the Document and other
  549. documents released under this License, and replace the individual
  550. copies of this License in the various documents with a single copy
  551. that is included in the collection, provided that you follow the
  552. rules of this License for verbatim copying of each of the
  553. documents in all other respects.
  554. You may extract a single document from such a collection, and
  555. distribute it individually under this License, provided you insert
  556. a copy of this License into the extracted document, and follow
  557. this License in all other respects regarding verbatim copying of
  558. that document.
  559. 7. AGGREGATION WITH INDEPENDENT WORKS
  560. A compilation of the Document or its derivatives with other
  561. separate and independent documents or works, in or on a volume of
  562. a storage or distribution medium, is called an "aggregate" if the
  563. copyright resulting from the compilation is not used to limit the
  564. legal rights of the compilation's users beyond what the individual
  565. works permit. When the Document is included in an aggregate, this
  566. License does not apply to the other works in the aggregate which
  567. are not themselves derivative works of the Document.
  568. If the Cover Text requirement of section 3 is applicable to these
  569. copies of the Document, then if the Document is less than one half
  570. of the entire aggregate, the Document's Cover Texts may be placed
  571. on covers that bracket the Document within the aggregate, or the
  572. electronic equivalent of covers if the Document is in electronic
  573. form. Otherwise they must appear on printed covers that bracket
  574. the whole aggregate.
  575. 8. TRANSLATION
  576. Translation is considered a kind of modification, so you may
  577. distribute translations of the Document under the terms of section
  578. 4. Replacing Invariant Sections with translations requires special
  579. permission from their copyright holders, but you may include
  580. translations of some or all Invariant Sections in addition to the
  581. original versions of these Invariant Sections. You may include a
  582. translation of this License, and all the license notices in the
  583. Document, and any Warranty Disclaimers, provided that you also
  584. include the original English version of this License and the
  585. original versions of those notices and disclaimers. In case of a
  586. disagreement between the translation and the original version of
  587. this License or a notice or disclaimer, the original version will
  588. prevail.
  589. If a section in the Document is Entitled "Acknowledgements",
  590. "Dedications", or "History", the requirement (section 4) to
  591. Preserve its Title (section 1) will typically require changing the
  592. actual title.
  593. 9. TERMINATION
  594. You may not copy, modify, sublicense, or distribute the Document
  595. except as expressly provided under this License. Any attempt
  596. otherwise to copy, modify, sublicense, or distribute it is void,
  597. and will automatically terminate your rights under this License.
  598. However, if you cease all violation of this License, then your
  599. license from a particular copyright holder is reinstated (a)
  600. provisionally, unless and until the copyright holder explicitly
  601. and finally terminates your license, and (b) permanently, if the
  602. copyright holder fails to notify you of the violation by some
  603. reasonable means prior to 60 days after the cessation.
  604. Moreover, your license from a particular copyright holder is
  605. reinstated permanently if the copyright holder notifies you of the
  606. violation by some reasonable means, this is the first time you have
  607. received notice of violation of this License (for any work) from
  608. that copyright holder, and you cure the violation prior to 30 days
  609. after your receipt of the notice.
  610. Termination of your rights under this section does not terminate
  611. the licenses of parties who have received copies or rights from
  612. you under this License. If your rights have been terminated and
  613. not permanently reinstated, receipt of a copy of some or all of
  614. the same material does not give you any rights to use it.
  615. 10. FUTURE REVISIONS OF THIS LICENSE
  616. The Free Software Foundation may publish new, revised versions of
  617. the GNU Free Documentation License from time to time. Such new
  618. versions will be similar in spirit to the present version, but may
  619. differ in detail to address new problems or concerns. See
  620. `http://www.gnu.org/copyleft/'.
  621. Each version of the License is given a distinguishing version
  622. number. If the Document specifies that a particular numbered
  623. version of this License "or any later version" applies to it, you
  624. have the option of following the terms and conditions either of
  625. that specified version or of any later version that has been
  626. published (not as a draft) by the Free Software Foundation. If
  627. the Document does not specify a version number of this License,
  628. you may choose any version ever published (not as a draft) by the
  629. Free Software Foundation. If the Document specifies that a proxy
  630. can decide which future versions of this License can be used, that
  631. proxy's public statement of acceptance of a version permanently
  632. authorizes you to choose that version for the Document.
  633. 11. RELICENSING
  634. "Massive Multiauthor Collaboration Site" (or "MMC Site") means any
  635. World Wide Web server that publishes copyrightable works and also
  636. provides prominent facilities for anybody to edit those works. A
  637. public wiki that anybody can edit is an example of such a server.
  638. A "Massive Multiauthor Collaboration" (or "MMC") contained in the
  639. site means any set of copyrightable works thus published on the MMC
  640. site.
  641. "CC-BY-SA" means the Creative Commons Attribution-Share Alike 3.0
  642. license published by Creative Commons Corporation, a not-for-profit
  643. corporation with a principal place of business in San Francisco,
  644. California, as well as future copyleft versions of that license
  645. published by that same organization.
  646. "Incorporate" means to publish or republish a Document, in whole or
  647. in part, as part of another Document.
  648. An MMC is "eligible for relicensing" if it is licensed under this
  649. License, and if all works that were first published under this
  650. License somewhere other than this MMC, and subsequently
  651. incorporated in whole or in part into the MMC, (1) had no cover
  652. texts or invariant sections, and (2) were thus incorporated prior
  653. to November 1, 2008.
  654. The operator of an MMC Site may republish an MMC contained in the
  655. site under CC-BY-SA on the same site at any time before August 1,
  656. 2009, provided the MMC is eligible for relicensing.
  657. ADDENDUM: How to use this License for your documents
  658. ====================================================
  659. To use this License in a document you have written, include a copy of
  660. the License in the document and put the following copyright and license
  661. notices just after the title page:
  662. Copyright (C) YEAR YOUR NAME.
  663. Permission is granted to copy, distribute and/or modify this document
  664. under the terms of the GNU Free Documentation License, Version 1.3
  665. or any later version published by the Free Software Foundation;
  666. with no Invariant Sections, no Front-Cover Texts, and no Back-Cover
  667. Texts. A copy of the license is included in the section entitled ``GNU
  668. Free Documentation License''.
  669. If you have Invariant Sections, Front-Cover Texts and Back-Cover
  670. Texts, replace the "with...Texts." line with this:
  671. with the Invariant Sections being LIST THEIR TITLES, with
  672. the Front-Cover Texts being LIST, and with the Back-Cover Texts
  673. being LIST.
  674. If you have Invariant Sections without Cover Texts, or some other
  675. combination of the three, merge those two alternatives to suit the
  676. situation.
  677. If your document contains nontrivial examples of program code, we
  678. recommend releasing these examples in parallel under your choice of
  679. free software license, such as the GNU General Public License, to
  680. permit their use in free software.
  681. 
  682. File: remember, Node: Concept Index, Prev: GNU Free Documentation License, Up: Top
  683. Index
  684. *****
  685. [index]
  686. * Menu:
  687. * diary, integration: Diary. (line 6)
  688. * mailbox, saving to: Mailbox. (line 6)
  689. * org mode, integration: Org. (line 6)
  690. * remember: Function Reference. (line 9)
  691. * remember-clipboard: Function Reference. (line 19)
  692. * remember-finalize: Function Reference. (line 24)
  693. * remember-mode: Function Reference. (line 27)
  694. * remember-region: Function Reference. (line 13)
  695. * text file, saving to: Text File. (line 6)
  696. 
  697. Tag Table:
  698. Node: Top1008
  699. Node: Preface2769
  700. Node: Introduction3114
  701. Node: Installation5461
  702. Node: Implementation5809
  703. Node: Quick Start8132
  704. Node: Function Reference10381
  705. Node: Keystrokes11564
  706. Node: Backends12004
  707. Node: Text File12421
  708. Node: Diary12839
  709. Node: Mailbox13237
  710. Node: Org13668
  711. Node: GNU Free Documentation License13891
  712. Node: Concept Index39064
  713. 
  714. End Tag Table