dotemacs

denote-autoloads.el (41608B)

---

 ;;; denote-autoloads.el --- automatically extracted autoloads (do not edit)   -*- lexical-binding: t -*-
 ;; Generated by the `loaddefs-generate' function.
 
 ;; This file is part of GNU Emacs.
 
 ;;; Code:
 
 (add-to-list 'load-path (or (and load-file-name (directory-file-name (file-name-directory load-file-name))) (car load-path)))
 
 
 
 ;;; Generated autoloads from denote.el
 
  (put 'denote-directory 'safe-local-variable (lambda (val) (or (stringp val) (eq val 'local) (eq val 'default-directory))))
  (put 'denote-known-keywords 'safe-local-variable #'listp)
  (put 'denote-infer-keywords 'safe-local-variable (lambda (val) (or val (null val))))
 (autoload 'denote "denote" "\
 Create a new note with the appropriate metadata and file name.
 
 Run the `denote-after-new-note-hook' after creating the new note.
 
 When called interactively, the metadata and file name are prompted
 according to the value of `denote-prompts'.
 
 When called from Lisp, all arguments are optional.
 
 - TITLE is a string or a function returning a string.
 
 - KEYWORDS is a list of strings.  The list can be empty or the
   value can be set to nil.
 
 - FILE-TYPE is a symbol among those described in `denote-file-type'.
 
 - SUBDIRECTORY is a string representing the path to either the
   value of the variable `denote-directory' or a subdirectory
   thereof.  The subdirectory must exist: Denote will not create
   it.  If SUBDIRECTORY does not resolve to a valid path, the
   variable `denote-directory' is used instead.
 
 - DATE is a string representing a date like 2022-06-30 or a date
   and time like 2022-06-16 14:30.  A nil value or an empty string
   is interpreted as the `current-time'.
 
 - TEMPLATE is a symbol which represents the key of a cons cell in
   the user option `denote-templates'.  The value of that key is
   inserted to the newly created buffer after the front matter.
 
 - SIGNATURE is a string or a function returning a string.
 
 (fn &optional TITLE KEYWORDS FILE-TYPE SUBDIRECTORY DATE TEMPLATE SIGNATURE)" t)
 (autoload 'denote-type "denote" "\
 Create note while prompting for a file type.
 
 This is the equivalent of calling `denote' when `denote-prompts'
 has the `file-type' prompt appended to its existing prompts." t)
 (function-put 'denote-type 'interactive-only 't)
 (autoload 'denote-date "denote" "\
 Create note while prompting for a date.
 
 The date can be in YEAR-MONTH-DAY notation like 2022-06-30 or
 that plus the time: 2022-06-16 14:30.  When the user option
 `denote-date-prompt-use-org-read-date' is non-nil, the date
 prompt uses the more powerful Org+calendar system.
 
 This is the equivalent of calling `denote' when `denote-prompts'
 has the `date' prompt appended to its existing prompts." t)
 (function-put 'denote-date 'interactive-only 't)
 (autoload 'denote-subdirectory "denote" "\
 Create note while prompting for a subdirectory.
 
 Available candidates include the value of the variable
 `denote-directory' and any subdirectory thereof.
 
 This is the equivalent of calling `denote' when `denote-prompts'
 has the `subdirectory' prompt appended to its existing prompts." t)
 (function-put 'denote-subdirectory 'interactive-only 't)
 (autoload 'denote-template "denote" "\
 Create note while prompting for a template.
 
 Available candidates include the keys in the `denote-templates'
 alist.  The value of the selected key is inserted in the newly
 created note after the front matter.
 
 This is the equivalent of calling `denote' when `denote-prompts'
 has the `template' prompt appended to its existing prompts." t)
 (function-put 'denote-template 'interactive-only 't)
 (autoload 'denote-signature "denote" "\
 Create note while prompting for a file signature.
 
 This is the equivalent of calling `denote' when `denote-prompts'
 has the `signature' prompt appended to its existing prompts." t)
 (function-put 'denote-signature 'interactive-only 't)
 (autoload 'denote-region "denote" "\
 Call `denote' and insert therein the text of the active region." t)
 (function-put 'denote-region 'interactive-only 't)
 (autoload 'denote-open-or-create "denote" "\
 Visit TARGET file in variable `denote-directory'.
 If file does not exist, invoke `denote' to create a file.
 
 If TARGET file does not exist, add the user input that was used
 to search for it to the minibuffer history of the
 `denote-file-prompt'.  The user can then retrieve and possibly
 further edit their last input, using it as the newly created
 note's actual title.  At the `denote-file-prompt' type
 \\<minibuffer-local-map>\\[previous-history-element].
 
 (fn TARGET)" t)
 (autoload 'denote-open-or-create-with-command "denote" "\
 Visit TARGET file in variable `denote-directory'.
 If file does not exist, invoke `denote' to create a file.
 
 If TARGET file does not exist, add the user input that was used
 to search for it to the minibuffer history of the
 `denote-file-prompt'.  The user can then retrieve and possibly
 further edit their last input, using it as the newly created
 note's actual title.  At the `denote-file-prompt' type
 \\<minibuffer-local-map>\\[previous-history-element]." t)
 (function-put 'denote-open-or-create-with-command 'interactive-only 't)
 (autoload 'denote-rename-file "denote" "\
 Rename file and update existing front matter if appropriate.
 
 Always rename the file where it is located in the file system:
 never move it to another directory.
 
 If in Dired, consider FILE to be the one at point, else prompt
 with minibuffer completion for one.  When called from Lisp, FILE
 is a file system path represented as a string.
 
 If FILE has a Denote-compliant identifier, retain it while
 updating components of the file name referenced by the user
 option `denote-prompts'.  By default, these are the TITLE and
 KEYWORDS.  The SIGNATURE is another one.  When called from Lisp,
 TITLE and SIGNATURE are strings, while KEYWORDS is a list of
 strings.
 
 If there is no identifier, create an identifier based on the
 following conditions:
 
 1. If the `denote-prompts' includes an entry for date prompts,
    then prompt for DATE and take its input to produce a new
    identifier.  For use in Lisp, DATE must conform with
    `denote-valid-date-p'.
 
 2. If DATE is nil (e.g. when `denote-prompts' does not include a
    date entry), use the file attributes to determine the last
    modified date of FILE and format it as an identifier.
 
 3. As a fallback, derive an identifier from the current date and
    time.
 
 4. At any rate, if the resulting identifier is not unique among
    the files in the variable `denote-directory', increment it
    such that it becomes unique.
 
 In interactive use, and assuming `denote-prompts' includes a
 title entry, make the TITLE prompt have prefilled text in the
 minibuffer that consists of the current title of FILE.  The
 current title is either retrieved from the front matter (such as
 the #+title in Org) or from the file name.
 
 Do the same for the SIGNATURE prompt, subject to `denote-prompts',
 by prefilling the minibuffer with the current signature of FILE,
 if any.
 
 Same principle for the KEYWORDS prompt: convert the keywords in
 the file name into a comma-separated string and prefill the
 minibuffer with it (the KEYWORDS prompt accepts more than one
 keywords, each separated by a comma, else the `crm-separator').
 
 For all prompts, interpret an empty input as an instruction to
 remove that file name component.  For example, if a TITLE prompt
 is available and FILE is 20240211T093531--some-title__keyword1.org
 then rename FILE to 20240211T093531__keyword1.org.
 
 If a file name component is present, but there is no entry for it in
 `denote-prompts', keep it as-is.
 
 [ NOTE: Please check with your minibuffer user interface how to
   provide an empty input.  The Emacs default setup accepts the
   empty minibuffer contents as they are, though popular packages
   like `vertico' use the first available completion candidate
   instead.  For `vertico', the user must either move one up to
   select the prompt and then type RET there with empty contents,
   or use the command `vertico-exit-input' with empty contents.
   That Vertico command is bound to M-RET as of this writing on
   2024-02-13 08:08 +0200. ]
 
 When renaming FILE, read its file type extension (like .org) and
 preserve it through the renaming process.  Files that have no
 extension are left without one.
 
 As a final step, ask for confirmation, showing the difference
 between old and new file names.  Do not ask for confirmation if
 the user option `denote-rename-no-confirm' is set to a non-nil
 value.
 
 If FILE has front matter for TITLE and KEYWORDS, ask to rewrite
 their values in order to reflect the new input, unless
 `denote-rename-no-confirm' is non-nil.  When the
 `denote-rename-no-confirm' is nil (the default), do not save the
 underlying buffer, thus giving the user the option to
 double-check the result, such as by invokling the command
 `diff-buffer-with-file'.  The rewrite of the TITLE and KEYWORDS
 in the front matter should not affect the rest of the front
 matter.
 
 If the file does not have front matter but is among the supported
 file types (per `denote-file-type'), add front matter to the top
 of it and leave the buffer unsaved for further inspection.  Save
 the buffer if `denote-rename-no-confirm' is non-nil.
 
 For the front matter of each file type, refer to the variables:
 
 - `denote-org-front-matter'
 - `denote-text-front-matter'
 - `denote-toml-front-matter'
 - `denote-yaml-front-matter'
 
 Run the `denote-after-rename-file-hook' after renaming FILE.
 
 This command is intended to (i) rename Denote files, (ii) convert
 existing supported file types to Denote notes, and (ii) rename
 non-note files (e.g. PDF) that can benefit from Denote's
 file-naming scheme.
 
 For a version of this command that works with multiple files
 one-by-one, use `denote-dired-rename-files'.
 
 (fn FILE &optional TITLE KEYWORDS SIGNATURE DATE)" t)
 (autoload 'denote-dired-rename-files "denote" "\
 Rename Dired marked files same way as `denote-rename-file'.
 Rename each file in sequence, making all the relevant prompts.
 Unlike `denote-rename-file', do not prompt for confirmation of
 the changes made to the file: perform them outright (same as
 setting `denote-rename-no-confirm' to a non-nil value)." '(dired-mode))
 (function-put 'denote-dired-rename-files 'interactive-only 't)
 (autoload 'denote-dired-rename-marked-files-with-keywords "denote" "\
 Rename marked files in Dired to a Denote file name by writing keywords.
 
 Specifically, do the following:
 
 - retain the file's existing name and make it the TITLE field,
   per Denote's file-naming scheme;
 
 - sluggify the TITLE, according to our conventions (check the
   user option `denote-file-name-slug-functions');
 
 - prepend an identifier to the TITLE;
 
 - preserve the file's extension, if any;
 
 - prompt once for KEYWORDS and apply the user's input to the
   corresponding field in the file name, rewriting any keywords
   that may exist while removing keywords that do exist if
   KEYWORDS is empty;
 
 - add or rewrite existing front matter to the underlying file, if
   it is recognized as a Denote note (per `denote-file-type'),
   such that it includes the new keywords.
 
 Run the `denote-after-rename-file-hook' after renaming is done.
 
 [ Note that the affected buffers are not saved, unless the user
   option `denote-rename-no-confirm' is non-nil.  Users can thus
   check them to confirm that the new front matter does not cause
   any problems (e.g. with the `diff-buffer-with-file' command).
   Multiple buffers can be saved in one go with the command
   `save-some-buffers' (read its doc string).  ]" '(dired-mode))
 (function-put 'denote-dired-rename-marked-files-with-keywords 'interactive-only 't)
 (autoload 'denote-rename-file-using-front-matter "denote" "\
 Rename FILE using its front matter as input.
 When called interactively, FILE is the return value of the
 function `buffer-file-name' which is subsequently inspected for
 the requisite front matter.  It is thus implied that the FILE has
 a file type that is supported by Denote, per `denote-file-type'.
 
 Unless NO-CONFIRM is non-nil (such as with a prefix argument),
 ask for confirmation, showing the difference between the old and
 the new file names.
 
 Never modify the identifier of the FILE, if any, even if it is
 edited in the front matter.  Denote considers the file name to be
 the source of truth in this case to avoid potential breakage with
 typos and the like.
 
 If NO-CONFIRM is non-nil (such as with a prefix argument) do not
 prompt for confirmation while renaming the file.  Do it outright.
 
 If optional SAVE-BUFFER is non-nil (such as with a double prefix
 argument), save the corresponding buffer.
 
 If the user option `denote-rename-no-confirm' is non-nil,
 interpret it the same way as a combination of NO-CONFIRM and
 SAVE-BUFFER.
 
 The identifier of the file, if any, is never modified even if it
 is edited in the front matter: Denote considers the file name to
 be the source of truth in this case, to avoid potential breakage
 with typos and the like.
 
 (fn FILE &optional NO-CONFIRM SAVE-BUFFER)" t)
 (autoload 'denote-dired-rename-marked-files-using-front-matter "denote" "\
 Call `denote-rename-file-using-front-matter' over the Dired marked files.
 Refer to the documentation of that command for the technicalities.
 
 Marked files must count as notes for the purposes of Denote,
 which means that they at least have an identifier in their file
 name and use a supported file type, per `denote-file-type'.
 Files that do not meet this criterion are ignored because Denote
 cannot know if they have front matter and what that may be." '(dired-mode))
 (autoload 'denote-keywords-add "denote" "\
 Prompt for KEYWORDS to add to the current note's front matter.
 When called from Lisp, KEYWORDS is a list of strings.
 
 Rename the file without further prompt so that its name reflects
 the new front matter, per `denote-rename-file-using-front-matter'.
 
 With an optional SAVE-BUFFER (such as a prefix argument when
 called interactively), save the buffer outright.  Otherwise leave
 the buffer unsaved for further review.
 
 If the user option `denote-rename-no-confirm' is non-nil,
 interpret it the same way as SAVE-BUFFER, making SAVE-BUFFER
 reduntant.
 
 Run `denote-after-rename-file-hook' as a final step.
 
 (fn KEYWORDS &optional SAVE-BUFFER)" t)
 (autoload 'denote-keywords-remove "denote" "\
 Prompt for keywords in current note and remove them.
 Keywords are retrieved from the file's front matter.
 
 Rename the file without further prompt so that its name reflects
 the new front matter, per `denote-rename-file-using-front-matter'.
 
 With an optional SAVE-BUFFER as a prefix argument, save the
 buffer outright.  Otherwise leave the buffer unsaved for further
 review.
 
 If the user option `denote-rename-no-confirm' is non-nil,
 interpret it the same way as SAVE-BUFFER, making SAVE-BUFFER
 reduntant.
 
 Run `denote-after-rename-file-hook' as a final step.
 
 (fn &optional SAVE-BUFFER)" t)
 (function-put 'denote-keywords-remove 'interactive-only 't)
 (autoload 'denote-rename-add-signature "denote" "\
 Add to FILE name the SIGNATURE.
 In interactive use, prompt for FILE, defaulting either to the current
 buffer's file or the one at point in a Dired buffer.  Also prompt for
 SIGNATURE, using the existing one, if any, as the initial value.
 
 When called from Lisp, FILE is a string pointing to a file system path
 and SIGNATURE is a string.
 
 Ask for confirmation before renaming the file to include the new
 signature.  Do it unless the user option `denote-rename-no-confirm' is
 set to a non-nil value.
 
 Once the operation is done, reload any Dired buffers and run the
 `denote-after-rename-file-hook'.
 
 Also see `denote-rename-remove-signature'.
 
 (fn FILE SIGNATURE)" t)
 (autoload 'denote-rename-remove-signature "denote" "\
 Remove the signature of FILE.
 In interactive use, prompt for FILE, defaulting either to the current
 buffer's file or the one at point in a Dired buffer.  When called from
 Lisp, FILE is a string pointing to a file system path.
 
 Ask for confirmation before renaming the file to remove its signature.
 Do it unless the user option `denote-rename-no-confirm' is set to a
 non-nil value.
 
 Once the operation is done, reload any Dired buffers and run the
 `denote-after-rename-file-hook'.
 
 Also see `denote-rename-add-signature'.
 
 (fn FILE)" t)
 (autoload 'denote-add-front-matter "denote" "\
 Insert front matter at the top of FILE.
 
 When called interactively, FILE is the return value of the
 function `buffer-file-name'.  FILE is checked to determine
 whether it is a note for Denote's purposes.
 
 TITLE is a string.  Interactively, it is the user input at the
 minibuffer prompt.
 
 KEYWORDS is a list of strings.  Interactively, it is the user
 input at the minibuffer prompt.  This one supports completion for
 multiple entries, each separated by the `crm-separator' (normally
 a comma).
 
 The purpose of this command is to help the user generate new
 front matter for an existing note (perhaps because the user
 deleted the previous one and could not undo the change).
 
 This command does not rename the file (e.g. to update the
 keywords).  To rename a file by reading its front matter as
 input, use `denote-rename-file-using-front-matter'.
 
 Note that this command is useful only for existing Denote notes.
 If the user needs to convert a generic text file to a Denote
 note, they can use one of the command which first rename the file
 to make it comply with our file-naming scheme and then add the
 relevant front matter.
 
 [ NOTE: Please check with your minibuffer user interface how to
   provide an empty input.  The Emacs default setup accepts the
   empty minibuffer contents as they are, though popular packages
   like `vertico' use the first available completion candidate
   instead.  For `vertico', the user must either move one up to
   select the prompt and then type RET there with empty contents,
   or use the command `vertico-exit-input' with empty contents.
   That Vertico command is bound to M-RET as of this writing on
   2024-02-29 09:24 +0200. ]
 
 (fn FILE TITLE KEYWORDS)" t)
 (autoload 'denote-change-file-type-and-front-matter "denote" "\
 Change file type of FILE and add an appropriate front matter.
 
 If in Dired, consider FILE to be the one at point, else prompt
 with minibuffer completion for one.
 
 Add a front matter in the format of the NEW-FILE-TYPE at the
 beginning of the file.
 
 Retrieve the title of FILE from a line starting with a title
 field in its front matter, depending on the previous file
 type (e.g.  #+title for Org).  The same process applies for
 keywords.
 
 As a final step, ask for confirmation, showing the difference
 between old and new file names.
 
 Important note: No attempt is made to modify any other elements
 of the file.  This needs to be done manually.
 
 (fn FILE NEW-FILE-TYPE)" t)
 (autoload 'denote-dired-mode "denote" "\
 Fontify all Denote-style file names.
 
 Add this or `denote-dired-mode-in-directories' to
 `dired-mode-hook'.
 
 This is a minor mode.  If called interactively, toggle the
 `Denote-Dired mode' mode.  If the prefix argument is positive,
 enable the mode, and if it is zero or negative, disable the mode.
 
 If called from Lisp, toggle the mode if ARG is `toggle'.  Enable
 the mode if ARG is nil, omitted, or is a positive number.
 Disable the mode if ARG is a negative number.
 
 To check whether the minor mode is enabled in the current buffer,
 evaluate `denote-dired-mode'.
 
 The mode's hook is called both when the mode is enabled and when
 it is disabled.
 
 (fn &optional ARG)" t)
 (autoload 'denote-dired-mode-in-directories "denote" "\
 Enable `denote-dired-mode' in `denote-dired-directories'.
 Add this function to `dired-mode-hook'.
 
 If `denote-dired-directories-include-subdirectories' is non-nil,
 also enable it in all subdirectories.")
 (autoload 'denote-link "denote" "\
 Create link to FILE note in variable `denote-directory' with DESCRIPTION.
 
 When called interactively, prompt for FILE using completion.  In
 this case, derive FILE-TYPE from the current buffer.
 
 The DESCRIPTION is returned by the function specified in variable
 `denote-link-description-function'.  If the region is active, its
 content is deleted and can be used as the description of the
 link.  The default value of `denote-link-description-function'
 returns the content of the active region, if any, else the title
 of the linked file is used as the description.  The title comes
 either from the front matter or the file name.  Note that if you
 change the default value of `denote-link-description-function',
 make sure to use the `region-text' parameter.  Regardless of the
 value of this user option, `denote-link' will always replace the
 content of the active region.
 
 With optional ID-ONLY as a non-nil argument, such as with a
 universal prefix (\\[universal-argument]), insert links with just
 the identifier and no further description.  In this case, the
 link format is always [[denote:IDENTIFIER]].  If the DESCRIPTION
 is empty, the link is also as if ID-ONLY were non-nil.  The
 default value of `denote-link-description-function' returns an
 empty string when the region is empty.  Thus, the link will have
 no description in this case.
 
 When called from Lisp, FILE is a string representing a full file
 system path.  FILE-TYPE is a symbol as described in
 `denote-file-type'.  DESCRIPTION is a string.  Whether the caller
 treats the active region specially, is up to it.
 
 (fn FILE FILE-TYPE DESCRIPTION &optional ID-ONLY)" t)
 (autoload 'denote-link-with-signature "denote" "\
 Insert link to file with signature.
 Prompt for file using minibuffer completion, limiting the list of
 candidates to files with a signature in their file name.
 
 By default, the description of the link includes the signature,
 if present, followed by the file's title, if any.
 
 For more advanced uses with Lisp, refer to the `denote-link'
 function." t)
 (function-put 'denote-link-with-signature 'interactive-only 't)
 (autoload 'denote-find-link "denote" "\
 Use minibuffer completion to visit linked file." t)
 (function-put 'denote-find-link 'interactive-only 't)
 (autoload 'denote-find-backlink "denote" "\
 Use minibuffer completion to visit backlink to current file.
 
 Like `denote-find-link', but select backlink to follow." t)
 (function-put 'denote-find-backlink 'interactive-only 't)
 (autoload 'denote-link-after-creating "denote" "\
 Create new note in the background and link to it directly.
 
 Use `denote' interactively to produce the new note.  Its doc
 string explains which prompts will be used and under what
 conditions.
 
 With optional ID-ONLY as a prefix argument create a link that
 consists of just the identifier.  Else try to also include the
 file's title.  This has the same meaning as in `denote-link'.
 
 For a variant of this, see `denote-link-after-creating-with-command'.
 
 IMPORTANT NOTE: Normally, `denote' does not save the buffer it
 produces for the new note.  This is a safety precaution to not
 write to disk unless the user wants it (e.g. the user may choose
 to kill the buffer, thus cancelling the creation of the note).
 However, for this command the creation of the note happens in the
 background and the user may miss the step of saving their buffer.
 We thus have to save the buffer in order to (i) establish valid
 links, and (ii) retrieve whatever front matter from the target
 file.  Though see `denote-save-buffer-after-creation'.
 
 (fn &optional ID-ONLY)" t)
 (autoload 'denote-link-after-creating-with-command "denote" "\
 Like `denote-link-after-creating' but prompt for note-making COMMAND.
 Use this to, for example, call `denote-signature' so that the
 newly created note has a signature as part of its file name.
 
 Optional ID-ONLY has the same meaning as in the command
 `denote-link-after-creating'.
 
 (fn COMMAND &optional ID-ONLY)" t)
 (autoload 'denote-link-or-create "denote" "\
 Use `denote-link' on TARGET file, creating it if necessary.
 
 If TARGET file does not exist, call `denote-link-after-creating'
 which runs the `denote' command interactively to create the file.
 The established link will then be targeting that new file.
 
 If TARGET file does not exist, add the user input that was used
 to search for it to the minibuffer history of the
 `denote-file-prompt'.  The user can then retrieve and possibly
 further edit their last input, using it as the newly created
 note's actual title.  At the `denote-file-prompt' type
 \\<minibuffer-local-map>\\[previous-history-element].
 
 With optional ID-ONLY as a prefix argument create a link that
 consists of just the identifier.  Else try to also include the
 file's title.  This has the same meaning as in `denote-link'.
 
 (fn TARGET &optional ID-ONLY)" t)
 (autoload 'denote-link-buttonize-buffer "denote" "\
 Make denote: links actionable buttons in the current buffer.
 
 Buttonization applies to the plain text and Markdown file types,
 per the user option `denote-file-types'.  It will not do anything
 in `org-mode' buffers, as buttons already work there.  If you do
 not use Markdown or plain text, then you do not need this.
 
 Links work when they point to a file inside the variable
 `denote-directory'.
 
 To buttonize links automatically add this function to the
 `find-file-hook'.  Or call it interactively for on-demand
 buttonization.
 
 When called from Lisp, with optional BEG and END as buffer
 positions, limit the process to the region in-between.
 
 (fn &optional BEG END)" t)
 (autoload 'denote-backlinks "denote" "\
 Produce a buffer with backlinks to the current note.
 
 The backlinks' buffer shows the file name of the note linking to
 the current note, as well as the context of each link.
 
 File names are fontified by Denote if the user option
 `denote-link-fontify-backlinks' is non-nil.  If this user option
 is nil, the buffer is fontified by Xref.
 
 The placement of the backlinks' buffer is controlled by the user
 option `denote-link-backlinks-display-buffer-action'.  By
 default, it will show up below the current window." t)
 (autoload 'denote-add-links "denote" "\
 Insert links to all notes matching REGEXP.
 Use this command to reference multiple files at once.
 Particularly useful for the creation of metanotes (read the
 manual for more on the matter).
 
 Optional ID-ONLY has the same meaning as in `denote-link': it
 inserts links with just the identifier.
 
 (fn REGEXP &optional ID-ONLY)" t)
 (autoload 'denote-link-dired-marked-notes "denote" "\
 Insert Dired marked FILES as links in BUFFER.
 
 FILES are Denote notes, meaning that they have our file-naming
 scheme, are writable/regular files, and use the appropriate file
 type extension (per `denote-file-type').  Furthermore, the marked
 files need to be inside the variable `denote-directory' or one of
 its subdirectories.  No other file is recognised (the list of
 marked files ignores whatever does not count as a note for our
 purposes).
 
 The BUFFER is one which visits a Denote note file.  If there are
 multiple buffers, prompt with completion for one among them.  If
 there isn't one, throw an error.
 
 With optional ID-ONLY as a prefix argument, insert links with
 just the identifier (same principle as with `denote-link').
 
 This command is meant to be used from a Dired buffer.
 
 (fn FILES BUFFER &optional ID-ONLY)" '(dired-mode))
 (defvar denote-menu-bar-mode t "\
 Non-nil if Denote-Menu-Bar mode is enabled.
 See the `denote-menu-bar-mode' command
 for a description of this minor mode.
 Setting this variable directly does not take effect;
 either customize it (see the info node `Easy Customization')
 or call the function `denote-menu-bar-mode'.")
 (custom-autoload 'denote-menu-bar-mode "denote" nil)
 (autoload 'denote-menu-bar-mode "denote" "\
 Show Denote menu bar.
 
 This is a global minor mode.  If called interactively, toggle the
 `Denote-Menu-Bar mode' mode.  If the prefix argument is positive,
 enable the mode, and if it is zero or negative, disable the mode.
 
 If called from Lisp, toggle the mode if ARG is `toggle'.  Enable
 the mode if ARG is nil, omitted, or is a positive number.
 Disable the mode if ARG is a negative number.
 
 To check whether the minor mode is enabled in the current buffer,
 evaluate `(default-value \\='denote-menu-bar-mode)'.
 
 The mode's hook is called both when the mode is enabled and when
 it is disabled.
 
 (fn &optional ARG)" t)
 (autoload 'denote-link-ol-follow "denote" "\
 Find file of type `denote:' matching LINK.
 LINK is the identifier of the note, optionally followed by a
 search option akin to that of standard Org `file:' link types.
 Read Info node `(org) Search Options'.
 
 Uses the function `denote-directory' to establish the path to the
 file.
 
 (fn LINK)")
 (autoload 'denote-link-ol-complete "denote" "\
 Like `denote-link' but for Org integration.
 This lets the user complete a link through the `org-insert-link'
 interface by first selecting the `denote:' hyperlink type.")
 (autoload 'denote-link-ol-store "denote" "\
 Handler for `org-store-link' adding support for denote: links.
 Also see the user option `denote-org-store-link-to-heading'.")
 (autoload 'denote-link-ol-export "denote" "\
 Export a `denote:' link from Org files.
 The LINK, DESCRIPTION, and FORMAT are handled by the export
 backend.
 
 (fn LINK DESCRIPTION FORMAT)")
 (eval-after-load 'org `(funcall ',(lambda nil (with-no-warnings (org-link-set-parameters "denote" :follow #'denote-link-ol-follow :face 'denote-faces-link :complete #'denote-link-ol-complete :store #'denote-link-ol-store :export #'denote-link-ol-export)))))
 (autoload 'denote-org-capture "denote" "\
 Create new note through `org-capture-templates'.
 Use this as a function that returns the path to the new file.
 The file is populated with Denote's front matter.  It can then be
 expanded with the usual specifiers or strings that
 `org-capture-templates' supports.
 
 This function obeys `denote-prompts', but it ignores `file-type',
 if present: it always sets the Org file extension for the created
 note to ensure that the capture process works as intended,
 especially for the desired output of the
 `denote-org-capture-specifiers' (which can include arbitrary
 text).
 
 Consult the manual for template samples.")
 (autoload 'denote-org-capture-with-prompts "denote" "\
 Like `denote-org-capture' but with optional prompt parameters.
 
 When called without arguments, do not prompt for anything.  Just
 return the front matter with title and keyword fields empty and
 the date and identifier fields specified.  Also make the file
 name consist of only the identifier plus the Org file name
 extension.
 
 Otherwise produce a minibuffer prompt for every non-nil value
 that corresponds to the TITLE, KEYWORDS, SUBDIRECTORY, DATE, and
 TEMPLATE arguments.  The prompts are those used by the standard
 `denote' command and all of its utility commands.
 
 When returning the contents that fill in the Org capture
 template, the sequence is as follows: front matter, TEMPLATE, and
 then the value of the user option `denote-org-capture-specifiers'.
 
 Important note: in the case of SUBDIRECTORY actual subdirectories
 must exist---Denote does not create them.  Same principle for
 TEMPLATE as templates must exist and are specified in the user
 option `denote-templates'.
 
 (fn &optional TITLE KEYWORDS SUBDIRECTORY DATE TEMPLATE)")
 (register-definition-prefixes "denote" '("denote-"))
 
 
 ;;; Generated autoloads from denote-journal-extras.el
 
 (autoload 'denote-journal-extras-new-entry "denote-journal-extras" "\
 Create a new journal entry in variable `denote-journal-extras-directory'.
 Use `denote-journal-extras-keyword' as a keyword for the newly
 created file.  Set the title of the new entry according to the
 value of the user option `denote-journal-extras-title-format'.
 
 With optional DATE as a prefix argument, prompt for a date.  If
 `denote-date-prompt-use-org-read-date' is non-nil, use the Org
 date selection module.
 
 When called from Lisp DATE is a string and has the same format as
 that covered in the documentation of the `denote' function.  It
 is internally processed by `denote-parse-date'.
 
 (fn &optional DATE)" t)
 (autoload 'denote-journal-extras-new-or-existing-entry "denote-journal-extras" "\
 Locate an existing journal entry or create a new one.
 A journal entry is one that has `denote-journal-extras-keyword' as
 part of its file name.
 
 If there are multiple journal entries for the current date,
 prompt for one using minibuffer completion.  If there is only
 one, visit it outright.  If there is no journal entry, create one
 by calling `denote-journal-extra-new-entry'.
 
 With optional DATE as a prefix argument, prompt for a date.  If
 `denote-date-prompt-use-org-read-date' is non-nil, use the Org
 date selection module.
 
 When called from Lisp, DATE is a string and has the same format
 as that covered in the documentation of the `denote' function.
 It is internally processed by `denote-parse-date'.
 
 (fn &optional DATE)" t)
 (autoload 'denote-journal-extras-link-or-create-entry "denote-journal-extras" "\
 Use `denote-link' on journal entry, creating it if necessary.
 A journal entry is one that has `denote-journal-extras-keyword' as
 part of its file name.
 
 If there are multiple journal entries for the current date,
 prompt for one using minibuffer completion.  If there is only
 one, link to it outright.  If there is no journal entry, create one
 by calling `denote-journal-extra-new-entry' and link to it.
 
 With optional DATE as a prefix argument, prompt for a date.  If
 `denote-date-prompt-use-org-read-date' is non-nil, use the Org
 date selection module.
 
 When called from Lisp, DATE is a string and has the same format
 as that covered in the documentation of the `denote' function.
 It is internally processed by `denote-parse-date'.
 
 With optional ID-ONLY as a prefix argument create a link that
 consists of just the identifier.  Else try to also include the
 file's title.  This has the same meaning as in `denote-link'.
 
 (fn &optional DATE ID-ONLY)" t)
 (register-definition-prefixes "denote-journal-extras" '("denote-journal-extras-"))
 
 
 ;;; Generated autoloads from denote-org-extras.el
 
 (autoload 'denote-org-extras-link-to-heading "denote-org-extras" "\
 Link to file and then specify a heading to extend the link to.
 
 The resulting link has the following pattern:
 
 [[denote:IDENTIFIER::#ORG-HEADING-CUSTOM-ID]][Description::Heading text]].
 
 Because only Org files can have links to individual headings,
 limit the list of possible files to those which include the .org
 file extension (remember that Denote works with many file types,
 per the user option `denote-file-type').
 
 The user option `denote-org-extras-store-link-to-heading'
 determined whether the `org-store-link' function can save a link
 to the current heading.  Such links look the same as those of
 this command, though the functionality defined herein is
 independent of it.
 
 To only link to a file, use the `denote-link' command." '(org-mode))
 (function-put 'denote-org-extras-link-to-heading 'interactive-only 't)
 (autoload 'denote-org-extras-extract-org-subtree "denote-org-extras" "\
 Create new Denote note using the current Org subtree as input.
 Remove the subtree from its current file and move its contents
 into a new Denote file (a subtree is a heading with all of its
 contents, including subheadings).
 
 Take the text of the subtree's top level heading and use it as
 the title of the new note.
 
 If the heading has any tags, use them as the keywords of the new
 note.  If the Org file has any #+filetags use them as well (Org's
 filetags are inherited by the headings).  If none of these are
 true and the user option `denote-prompts' includes an entry for
 keywords, then prompt for keywords.  Else do not include any
 keywords.
 
 If the heading has a PROPERTIES drawer, retain it for further
 review.
 
 If the heading's PROPERTIES drawer includes a DATE or CREATED
 property, or there exists a CLOSED statement with a timestamp
 value, use that to derive the date (or date and time) of the new
 note (if there is only a date, the time is taken as 00:00).  If
 more than one of these is present, the order of preference is
 DATE, then CREATED, then CLOSED.  If none of these is present,
 use the current time.  If the `denote-prompts' includes an entry
 for a date, then prompt for a date at this stage (also see
 `denote-date-prompt-use-org-read-date').
 
 For the rest, consult the value of the user option
 `denote-prompts' in the following scenaria:
 
 - Optionally prompt for a subdirectory, otherwise produce the new
   note in the variable `denote-directory'.
 
 - Optionally prompt for a file signature, otherwise do not use
   one.
 
 Make the new note an Org file regardless of the value of
 `denote-file-type'." '(org-mode))
 (autoload 'denote-org-extras-convert-links-to-file-type "denote-org-extras" "\
 Convert denote: links to file: links in the current Org buffer.
 Ignore all other link types.  Also ignore links that do not
 resolve to a file in the variable `denote-directory'." '(org-mode))
 (autoload 'denote-org-extras-convert-links-to-denote-type "denote-org-extras" "\
 Convert file: links to denote: links in the current Org buffer.
 Ignore all other link types.  Also ignore file: links that do not
 point to a file with a Denote file name." '(org-mode))
 (autoload 'denote-org-extras-dblock-insert-links "denote-org-extras" "\
 Create Org dynamic block to insert Denote links matching REGEXP.
 
 (fn REGEXP)" '(org-mode))
 (autoload 'denote-org-extras-dblock-insert-missing-links "denote-org-extras" "\
 Create Org dynamic block to insert Denote links matching REGEXP.
 
 (fn REGEXP)" '(org-mode))
 (autoload 'denote-org-extras-dblock-insert-backlinks "denote-org-extras" "\
 Create Org dynamic block to insert Denote backlinks to current file." '(org-mode))
 (autoload 'denote-org-extras-dblock-insert-files "denote-org-extras" "\
 Create Org dynamic block to insert Denote files matching REGEXP.
 Sort the files according to SORT-BY-COMPONENT, which is a symbol
 among `denote-sort-components'.
 
 (fn REGEXP SORT-BY-COMPONENT)" '(org-mode))
 (register-definition-prefixes "denote-org-extras" '("denote-org-extras-" "org-dblock-write:denote-"))
 
 
 ;;; Generated autoloads from denote-rename-buffer.el
 
 (defvar denote-rename-buffer-mode nil "\
 Non-nil if Denote-Rename-Buffer mode is enabled.
 See the `denote-rename-buffer-mode' command
 for a description of this minor mode.
 Setting this variable directly does not take effect;
 either customize it (see the info node `Easy Customization')
 or call the function `denote-rename-buffer-mode'.")
 (custom-autoload 'denote-rename-buffer-mode "denote-rename-buffer" nil)
 (autoload 'denote-rename-buffer-mode "denote-rename-buffer" "\
 Automatically rename Denote buffers to be easier to read.
 
 A buffer is renamed upon visiting the underlying file.  This
 means that existing buffers are not renamed until they are
 visited again in a new buffer (files are visited with the command
 `find-file' or related).
 
 This is a global minor mode.  If called interactively, toggle the
 `Denote-Rename-Buffer mode' mode.  If the prefix argument is
 positive, enable the mode, and if it is zero or negative, disable
 the mode.
 
 If called from Lisp, toggle the mode if ARG is `toggle'.  Enable
 the mode if ARG is nil, omitted, or is a positive number.
 Disable the mode if ARG is a negative number.
 
 To check whether the minor mode is enabled in the current buffer,
 evaluate `(default-value \\='denote-rename-buffer-mode)'.
 
 The mode's hook is called both when the mode is enabled and when
 it is disabled.
 
 (fn &optional ARG)" t)
 (register-definition-prefixes "denote-rename-buffer" '("denote-rename-buffer"))
 
 
 ;;; Generated autoloads from denote-silo-extras.el
 
 (autoload 'denote-silo-extras-create-note "denote-silo-extras" "\
 Select SILO and run `denote' in it.
 SILO is a file path from `denote-silo-extras-directories'.
 
 When called from Lisp, SILO is a file system path to a directory.
 
 (fn SILO)" t)
 (autoload 'denote-silo-extras-open-or-create "denote-silo-extras" "\
 Select SILO and run `denote-open-or-create' in it.
 SILO is a file path from `denote-silo-extras-directories'.
 
 When called from Lisp, SILO is a file system path to a directory.
 
 (fn SILO)" t)
 (autoload 'denote-silo-extras-select-silo-then-command "denote-silo-extras" "\
 Select SILO and run Denote COMMAND in it.
 SILO is a file path from `denote-silo-extras-directories', while
 COMMAND is one among `denote-silo-extras-commands'.
 
 When called from Lisp, SILO is a file system path to a directory.
 
 (fn SILO COMMAND)" t)
 (register-definition-prefixes "denote-silo-extras" '("denote-silo-extras-"))
 
 
 ;;; Generated autoloads from denote-sort.el
 
 (autoload 'denote-sort-files "denote-sort" "\
 Returned sorted list of Denote FILES.
 
 With COMPONENT as a symbol among `denote-sort-components',
 sort files based on the corresponding file name component.
 
 With COMPONENT as a nil value keep the original date-based
 sorting which relies on the identifier of each file name.
 
 With optional REVERSE as a non-nil value, reverse the sort order.
 
 (fn FILES COMPONENT &optional REVERSE)")
 (autoload 'denote-sort-dired "denote-sort" "\
 Produce Dired dired-buffer with sorted files from variable `denote-directory'.
 When called interactively, prompt for FILES-MATCHING-REGEXP,
 SORT-BY-COMPONENT, and REVERSE.
 
 1. FILES-MATCHING-REGEXP limits the list of Denote files to
    those matching the provided regular expression.
 
 2. SORT-BY-COMPONENT sorts the files by their file name
    component (one among `denote-sort-components').
 
 3. REVERSE is a boolean to reverse the order when it is a non-nil value.
 
 When called from Lisp, the arguments are a string, a keyword, and
 a non-nil value, respectively.
 
 (fn FILES-MATCHING-REGEXP SORT-BY-COMPONENT REVERSE)" t)
 (register-definition-prefixes "denote-sort" '("denote-sort-"))
 
 ;;; End of scraped data
 
 (provide 'denote-autoloads)
 
 ;; Local Variables:
 ;; version-control: never
 ;; no-byte-compile: t
 ;; no-update-autoloads: t
 ;; no-native-compile: t
 ;; coding: utf-8-emacs-unix
 ;; End:
 
 ;;; denote-autoloads.el ends here