{"diffoscope-json-version": 1, "source1": "/srv/reproducible-results/rbuild-debian/r-b-build.OuRvVYI5/b1/yasnippet_0.14.0+git20230912.76e1eee6-2_arm64.changes", "source2": "/srv/reproducible-results/rbuild-debian/r-b-build.OuRvVYI5/b2/yasnippet_0.14.0+git20230912.76e1eee6-2_arm64.changes", "unified_diff": null, "details": [{"source1": "Files", "source2": "Files", "unified_diff": "@@ -1,3 +1,3 @@\n \n- c97d55c6899e6efab021b928e16ebfc2 531132 lisp optional elpa-yasnippet_0.14.0+git20230912.76e1eee6-2_all.deb\n+ 7571630bb5e0217d06b776700882e2c2 530968 lisp optional elpa-yasnippet_0.14.0+git20230912.76e1eee6-2_all.deb\n 8163e017e33c3495e2c2cf992d5ca517 3352 lisp optional yasnippet_0.14.0+git20230912.76e1eee6-2_all.deb\n"}, {"source1": "elpa-yasnippet_0.14.0+git20230912.76e1eee6-2_all.deb", "source2": "elpa-yasnippet_0.14.0+git20230912.76e1eee6-2_all.deb", "unified_diff": null, "details": [{"source1": "file list", "source2": "file list", "unified_diff": "@@ -1,3 +1,3 @@\n -rw-r--r-- 0 0 0 4 2024-07-26 02:45:37.000000 debian-binary\n -rw-r--r-- 0 0 0 1992 2024-07-26 02:45:37.000000 control.tar.xz\n--rw-r--r-- 0 0 0 528948 2024-07-26 02:45:37.000000 data.tar.xz\n+-rw-r--r-- 0 0 0 528784 2024-07-26 02:45:37.000000 data.tar.xz\n"}, {"source1": "control.tar.xz", "source2": "control.tar.xz", "unified_diff": null, "details": [{"source1": "control.tar", "source2": "control.tar", "unified_diff": null, "details": [{"source1": "./md5sums", "source2": "./md5sums", "unified_diff": null, "details": [{"source1": "./md5sums", "source2": "./md5sums", "comments": ["Files differ"], "unified_diff": null}]}]}]}, {"source1": "data.tar.xz", "source2": "data.tar.xz", "unified_diff": null, "details": [{"source1": "data.tar", "source2": "data.tar", "unified_diff": null, "details": [{"source1": "./usr/share/doc/elpa-yasnippet/html/faq.html", "source2": "./usr/share/doc/elpa-yasnippet/html/faq.html", "unified_diff": "@@ -214,55 +214,55 @@\n \n
\n

Frequently Asked Questions

\n
\n

Table of Contents

\n \n
\n \n \n-
\n-

Why are my snippet abbrev keys triggering when I don't want them too?

\n-
\n+
\n+

Why are my snippet abbrev keys triggering when I don't want them too?

\n+
\n

\n Expansion of abbrev keys is controlled by yas-key-syntaxes. Try\n removing entries which correspond to the abbrev key character syntax.\n For example, if you have a snippet with abbrev key \"bar\", that you\n don't want to trigger when point follows the text foo_bar, remove\n the \"w\" entry (since \"bar\" has only word syntax characters).\n

\n
\n
\n \n-
\n-

Why aren't my snippet abbrev keys triggering when I want them too?

\n-
\n+
\n+

Why aren't my snippet abbrev keys triggering when I want them too?

\n+
\n

\n See previous question, but in reverse.\n

\n
\n
\n \n-
\n-

Why is there an extra newline?

\n-
\n+
\n+

Why is there an extra newline?

\n+
\n

\n If there is a newline at the end of a snippet definition file,\n YASnippet will add a newline when expanding that snippet. When editing\n or saving a snippet file, please be careful not to accidentally add a\n terminal newline.\n

\n \n@@ -270,17 +270,17 @@\n Note that some editors will automatically add a newline for you. In\n Emacs, if you set require-final-newline to t, it will add the\n final newline automatically.\n

\n
\n
\n \n-
\n-

Why doesn't TAB navigation work with flyspell

\n-
\n+
\n+

Why doesn't TAB navigation work with flyspell

\n+
\n

\n This is Emacs Bug#26672, so you should upgrade to version 25.3 or\n better. Otherwise, a workaround is to inhibit flyspell overlays while\n the snippet is active:\n

\n \n
\n@@ -289,17 +289,17 @@\n (and yas-active-field-overlay\n (overlay-buffer yas-active-field-overlay))))\n \n
\n
\n
\n \n-
\n-

How do I use alternative keys, i.e. not TAB?

\n-
\n+
\n+

How do I use alternative keys, i.e. not TAB?

\n+
\n

\n Edit the keymaps yas-minor-mode-map and yas-keymap as you would\n any other keymap, but use yas-filtered-definition on the definition\n if you want to respect yas-keymap-disable-hook:\n

\n \n
\n@@ -317,17 +317,17 @@\n (define-key yas-keymap (kbd \"<new-prev-field-key>\")\n (yas-filtered-definition 'yas-prev-field))\n \n
\n
\n
\n \n-
\n-

How do I define an abbrev key containing characters not supported by the filesystem?

\n-
\n+
\n+

How do I define an abbrev key containing characters not supported by the filesystem?

\n+
\n
    \n
  • Note: This question applies if you're still defining snippets\n whose key is the filename. This is behavior still provided by\n version 0.6 for backward compatibilty, but is somewhat\n deprecated…
    • \n
\n \n"}, {"source1": "./usr/share/doc/elpa-yasnippet/html/snippet-development.html", "source2": "./usr/share/doc/elpa-yasnippet/html/snippet-development.html", "unified_diff": "@@ -214,98 +214,98 @@\n
\n
\n

Writing snippets

\n \n \n-
\n-

Snippet development

\n-
\n-
\n-
\n-

Quickly finding snippets

\n-
\n+
\n+

Snippet development

\n+
\n+
\n+
\n+

Quickly finding snippets

\n+
\n

\n There are some ways you can quickly find a snippet file or create a new one:\n

\n \n
    \n

  • \n M-x yas-new-snippet, key binding: C-c & C-n\n

    \n \n

    \n Creates a new buffer with a template for making a new snippet. The\n-buffer is in snippet-mode (see below). When you are done editing\n-the new snippet, use C-c C-c to save it.\n+buffer is in snippet-mode (see below). When you are done editing\n+the new snippet, use C-c C-c to save it.\n

    • \n \n

  • \n M-x yas-visit-snippet-file, key binding: C-c & C-v\n

    \n \n

    \n Prompts you for possible snippet expansions like\n yas-insert-snippet, but instead of expanding it, takes you directly\n to the snippet definition's file, if it exists.\n

    • \n
\n \n

\n-Once you find this file it will be set to snippet-mode (see ahead)\n+Once you find this file it will be set to snippet-mode (see ahead)\n and you can start editing your snippet.\n

\n
\n
\n \n-
\n-

Using the snippet-mode major mode

\n-
\n+
\n+

Using the snippet-mode major mode

\n+
\n

\n There is a major mode snippet-mode to edit snippets. You can set the\n buffer to this mode with M-x snippet-mode. It provides reasonably\n useful syntax highlighting.\n

\n \n

\n@@ -320,15 +320,15 @@\n

\n Prompts for a snippet table (with a default based on snippet's\n major mode) and loads the snippet currently being edited.\n

\n \n

  • \n M-x yas-load-snippet-buffer-and-close, key binding: C-c C-c\n-\n+\n

    \n \n

    \n Like yas-load-snippet-buffer, but also saves the snippet and\n calls quit-window. The destination is decided based on the\n chosen snippet table and snippet collection directly (defaulting to\n the first directory in yas-snippet-dirs (see Organizing Snippets\n@@ -350,17 +350,17 @@\n There are also snippets for writing snippets: vars, $f and $m\n :-).\n

    \n
    • \n
    \n
    \n \n-
    \n-

    File content

    \n-
    \n+
    \n+

    File content

    \n+
    \n

    \n A file defining a snippet generally contains the template to be\n expanded.\n

    \n \n

    \n Optionally, if the file contains a line of # --, the lines above it\n@@ -383,61 +383,61 @@\n

    \n \n

    \n Here's a list of currently supported directives:\n

    \n
    \n \n-
    \n-

    # key: snippet abbrev

    \n-
    \n+
    \n+

    # key: snippet abbrev

    \n+
    \n

    \n This is the probably the most important directive, it's the\n abbreviation you type to expand a snippet just before hitting the key\n that runs yas-expand. If you don't specify this,\n the snippet will not be expandable through the trigger mechanism.\n

    \n
    \n
    \n \n-
    \n-

    # name: snippet name

    \n-
    \n+
    \n+

    # name: snippet name

    \n+
    \n

    \n This is a one-line description of the snippet. It will be displayed in\n the menu. It's a good idea to select a descriptive name for a snippet –\n especially distinguishable among similar snippets.\n

    \n \n

    \n If you omit this name, it will default to the file name the snippet\n was loaded from.\n

    \n
    \n
    \n \n-
    \n-

    # condition: snippet condition

    \n-
    \n+
    \n+

    # condition: snippet condition

    \n+
    \n

    \n This is a piece of Emacs Lisp code. If a snippet has a condition, then\n it will only be expanded when the condition code evaluate to some\n non-nil value.\n

    \n \n

    \n See also yas-buffer-local-condition in\n Expanding snippets\n

    \n
    \n
    \n \n-
    \n-

    # group: snippet menu grouping

    \n-
    \n+
    \n+

    # group: snippet menu grouping

    \n+
    \n

    \n When expanding/visiting snippets from the menu-bar menu, snippets for a\n given mode can be grouped into sub-menus. This is useful if one has too\n many snippets for a mode which will make the menu too long.\n

    \n \n

    \n@@ -453,17 +453,17 @@\n # group: directive. Group can also be nested, e.g.\n control structure.loops indicates that the snippet is under the loops\n group which is under the control structure group.\n

    \n
    \n
    \n \n-
    \n-

    # expand-env: expand environment

    \n-
    \n+
    \n+

    # expand-env: expand environment

    \n+
    \n

    \n This is another piece of Emacs Lisp code in the form of a let varlist\n form, i.e. a list of lists assigning values to variables. It can be\n used to override variable values while the snippet is being expanded.\n

    \n \n

    \n@@ -493,17 +493,17 @@\n | | | |\n +--+-+--+\n \n

    \n
    \n
    \n \n-
    \n-

    # binding: direct keybinding

    \n-
    \n+
    \n+

    # binding: direct keybinding

    \n+
    \n

    \n You can use this directive to expand a snippet directly from a normal\n Emacs keybinding. The keybinding will be registered in the Emacs keymap\n named after the major mode the snippet is active for.\n

    \n \n

    \n@@ -524,77 +524,77 @@\n This binding will be recorded in the keymap html-mode-map. To expand a\n paragraph tag newlines, just press C-u C-c C-c C-m. Omitting the C-u\n will expand the paragraph tag without newlines.\n

    \n
    \n
    \n \n-
    \n-

    # type: snippet or command

    \n-
    \n+
    \n+

    # type: snippet or command

    \n+
    \n

    \n If the type directive is set to command, the body of the snippet\n is interpreted as Lisp code to be evaluated when the snippet is\n triggered.\n

    \n \n

    \n If it's snippet (the default when there is no type directive), the\n-snippet body will be parsed according to the Template Syntax,\n+snippet body will be parsed according to the Template Syntax,\n described below.\n

    \n
    \n
    \n \n-
    \n-

    # uuid: unique identifier

    \n-
    \n+
    \n+

    # uuid: unique identifier

    \n+
    \n

    \n This provides to a way to identify a snippet, independent of its name.\n Loading a second snippet file with the same uuid would replace the\n previous snippet.\n

    \n
    \n
    \n \n-
    \n-

    # contributor: snippet author

    \n-
    \n+
    \n+

    # contributor: snippet author

    \n+
    \n

    \n This is optional and has no effect whatsoever on snippet functionality,\n but it looks nice.\n

    \n
    \n
    \n
    \n \n-
    \n-

    Template Syntax

    \n-
    \n+
    \n+

    Template Syntax

    \n+
    \n

    \n The syntax of the snippet template is simple but powerful, very similar\n to TextMate's.\n

    \n
    \n \n-
    \n-

    Plain Text

    \n-
    \n+
    \n+

    Plain Text

    \n+
    \n

    \n Arbitrary text can be included as the content of a template. They are\n usually interpreted as plain text, except $ and `. You need to\n use \\ to escape them: \\$ and \\`. The \\ itself may also needed to be\n escaped as \\\\ sometimes.\n

    \n
    \n
    \n \n-
    \n-

    Embedded Emacs Lisp code

    \n-
    \n+
    \n+

    Embedded Emacs Lisp code

    \n+
    \n

    \n Emacs Lisp code can be embedded inside the template, written inside\n back-quotes (`). The Lisp forms are evaluated when the snippet is\n being expanded. The evaluation is done in the same buffer as the\n snippet being expanded.\n

    \n \n@@ -629,17 +629,17 @@\n

    \n to \"wrap\" the selected region inside your recently inserted snippet.\n Alternatively, you can also customize the variable\n yas-wrap-around-region to t which will do this automatically.\n

    \n
    \n \n-
    \n-

    Note: backquote expressions should not modify the buffer

    \n-
    \n+
    \n+

    Note: backquote expressions should not modify the buffer

    \n+
    \n

    \n Please note that the Lisp forms in backquotes should not modify the\n buffer, doing so will trigger a warning. For example, instead of\n doing\n

    \n \n
    \n@@ -663,17 +663,17 @@\n \n
    \n
    \n
    \n
    \n \n \n-
    \n-

    Tab stop fields

    \n-
    \n+
    \n+

    Tab stop fields

    \n+
    \n

    \n Tab stops are fields that you can navigate back and forth by TAB and\n S-TAB. They are written by $ followed with a number. $0 has the\n special meaning of the exit point of a snippet. That is the last place\n to go when you've traveled all the fields. Here's a typical example:\n

    \n \n@@ -681,39 +681,39 @@\n 
    <div$1>\n     $0\n </div>\n
    \n
    \n
    \n
    \n-
    \n-

    Placeholder fields

    \n-
    \n+
    \n+

    Placeholder fields

    \n+
    \n

    \n Tab stops can have default values – a.k.a placeholders. The syntax is\n like this:\n

    \n \n
    \n 
    ${N:default value}\n
    \n
    \n \n

    \n They act as the default value for a tab stop. But when you first\n type at a tab stop, the default value will be replaced by your typing.\n-The number can be omitted if you don't want to create mirrors or\n-transformations for this field.\n+The number can be omitted if you don't want to create mirrors or\n+transformations for this field.\n

    \n
    \n
    \n \n-
    \n-

    Mirrors

    \n-
    \n+
    \n+

    Mirrors

    \n+
    \n

    \n We refer to tab stops with placeholders as a field. A field can\n have mirrors. All mirrors get updated whenever you update any field\n text. Here's an example:\n

    \n \n
    \n@@ -733,17 +733,17 @@\n The tab stops with the same number to the field act as its mirrors. If\n none of the tab stops have an initial value, the first one is selected as\n the field and the others are its mirrors.\n

    \n
    \n
    \n \n-
    \n-

    Mirrors with transformations

    \n-
    \n+
    \n+

    Mirrors with transformations

    \n+
    \n

    \n If the value of an ${n:-construct starts with and contains $(,\n then it is interpreted as a mirror for field n with a\n transformation. The mirror's text content is calculated according to\n this transformation, which is Emacs Lisp code that gets evaluated in\n an environment where the variable yas-text is bound to the text\n content (string) contained in the field n. Here's an example for\n@@ -829,17 +829,17 @@\n

    \n To keep the example simple, it uses ignore-errors to suppress errors\n due to incomplete format codes.\n

    \n
    \n
    \n \n-
    \n-

    Fields with transformations

    \n-
    \n+
    \n+

    Fields with transformations

    \n+
    \n

    \n From version 0.6 on, you can also have Lisp transformation inside\n fields. These work mostly like mirror transformations. However, they\n are evaluated when you first enter the field, after each change you\n make to the field and also just before you exit the field.\n

    \n \n@@ -876,17 +876,17 @@\n value of the field and sets it its internal modification state to\n true. As a consequence, the auto-deletion behaviour of normal fields\n does not take place. This is by design.\n

    \n
    \n
    \n \n-
    \n-

    Choosing fields value from a list and other tricks

    \n-
    \n+
    \n+

    Choosing fields value from a list and other tricks

    \n+
    \n

    \n As mentioned, the field transformation is invoked just after you enter\n the field, and with some useful variables bound, notably\n yas-modified-p and yas-moving-away-p. Because of this feature you\n can place a transformation in the primary field that lets you select\n default values for it.\n

    \n@@ -937,17 +937,17 @@\n

    \n The function yas-verify-value has another neat trick, and makes use\n of yas-moving-away-p. Try it and see! Also, check out this thread\n

    \n
    \n
    \n \n-
    \n-

    Nested placeholder fields

    \n-
    \n+
    \n+

    Nested placeholder fields

    \n+
    \n

    \n From version 0.6 on, you can also have nested placeholders of the type:\n

    \n \n
    \n 
    <div${1: id=\"${2:some_id}\"}>$0</div>\n
    \n@@ -965,17 +965,17 @@\n By the way, C-d will only clear the field if you cursor is at the\n beginning of the field and it hasn't been changed yet. Otherwise, it\n performs the normal Emacs delete-char command.\n

    \n
    \n
    \n \n-
    \n-

    Indentation markers

    \n-
    \n+
    \n+

    Indentation markers

    \n+
    \n

    \n If yas-indent-line is not set to 'auto, it's still possible to\n indent specific lines by adding an indentation marker, $>, somewhere\n on the line.\n

    \n
    \n
    \n"}, {"source1": "./usr/share/doc/elpa-yasnippet/html/snippet-expansion.html", "source2": "./usr/share/doc/elpa-yasnippet/html/snippet-expansion.html", "unified_diff": "@@ -214,42 +214,42 @@\n
    \n
    \n

    Expanding snippets

    \n \n@@ -258,17 +258,17 @@\n

    \n \n

    \n Maybe, you'll want some snippets to be expanded in a particular\n mode, or only under certain conditions, or be prompted using\n

    \n \n-
    \n-

    Triggering expansion

    \n-
    \n+
    \n+

    Triggering expansion

    \n+
    \n

    \n You can use YASnippet to expand snippets in different ways:\n

    \n \n
      \n
    • When yas-minor-mode is active:\n
        \n@@ -288,17 +288,17 @@\n
      • Use m2m's excellent auto-complete\n TODO: example for this
        • \n \n
      • Expanding from emacs-lisp code
        • \n
      \n
    \n \n-
    \n-

    Trigger key

    \n-
    \n+
    \n+

    Trigger key

    \n+
    \n

    \n yas-expand tries to expand a snippet abbrev (also known as\n snippet key) before point. YASnippet also provides a conditional\n binding for this command: the variable yas-maybe-expand contains a\n special value which, when bound in a keymap, tells Emacs to call\n yas-expand if and only if there is a snippet abbrev before point.\n If there is no snippet to expand, Emacs will behave as if yas-expand\n@@ -334,41 +334,41 @@\n

    \n To enable the YASnippet minor mode in all buffers globally use the\n command yas-global-mode. This will enable a modeline indicator,\n yas:\n

    \n \n \n-
    \n+
    \n

    \"minor-mode-indicator.png\"\n

    \n
    \n \n

    \n When you use yas-global-mode you can also selectively disable\n YASnippet in some buffers by calling yas-minor-mode with a negative\n argument in the buffer's mode hook.\n

    \n
    \n \n-
    \n-

    Fallback behaviour

    \n-
    \n+
    \n+

    Fallback behaviour

    \n+
    \n

    \n YASnippet used to support a more complicated way of sharing\n keybindings before yas-maybe-expand was added. This is now\n obsolete.\n

    \n
    \n
    \n
    \n \n-
    \n-

    Insert at point

    \n-
    \n+
    \n+

    Insert at point

    \n+
    \n

    \n The command yas-insert-snippet lets you insert snippets at point\n for your current major mode. It prompts you for the snippet key\n first, and then for a snippet template if more than one template\n exists for the same key.\n

    \n \n@@ -380,17 +380,17 @@\n \n

    \n The prompting methods used are again controlled by\n yas-prompt-functions.\n

    \n
    \n \n-
    \n-

    Inserting region or register contents into snippet

    \n-
    \n+
    \n+

    Inserting region or register contents into snippet

    \n+
    \n

    \n It's often useful to inject already written text in the middle of a\n snippet. The variable yas-wrap-around-region when to t substitute\n the region contents into the $0 placeholder of a snippet expanded by\n yas-insert-snippet. Setting it to a character value (e.g. ?0)\n will insert the contents of corresponding register.\n

    \n@@ -401,49 +401,49 @@\n turned on. This setting is still supported for backwards\n compatibility, but is now entirely equivalent to ?0.\n

    \n
    \n
    \n
    \n \n-
    \n-

    Snippet keybinding

    \n-
    \n+
    \n+

    Snippet keybinding

    \n+
    \n

    \n See the section of the # binding: directive in\n Writing Snippets.\n

    \n
    \n
    \n \n-
    \n-

    Expanding from the menu

    \n-
    \n+
    \n+

    Expanding from the menu

    \n+
    \n

    \n See the YASnippet Menu.\n

    \n
    \n
    \n \n-
    \n-

    Expanding with hippie-expand

    \n-
    \n+
    \n+

    Expanding with hippie-expand

    \n+
    \n

    \n To integrate with hippie-expand, just put\n yas-hippie-try-expand in\n hippie-expand-try-functions-list. This probably makes more sense\n when placed at the top of the list, but it can be put anywhere you\n prefer.\n

    \n
    \n
    \n \n-
    \n-

    Expanding from emacs-lisp code

    \n-
    \n+
    \n+

    Expanding from emacs-lisp code

    \n+
    \n

    \n Sometimes you might want to expand a snippet directly from your own\n elisp code. You should call yas-expand-snippet instead of\n yas-expand in this case. yas-expand-snippet takes a string in\n snippet template syntax, if you want to expand an existing snippet you\n can use yas-lookup-snippet to find its contents by name.\n

    \n@@ -464,21 +464,21 @@\n See the internal documentation on yas-expand-snippet and\n yas-lookup-snippet for more information.\n

    \n
    \n
    \n
    \n \n-
    \n-

    Controlling expansion

    \n-
    \n-
    \n-
    \n-

    Eligible snippets

    \n-
    \n+
    \n+

    Controlling expansion

    \n+
    \n+
    \n+
    \n+

    Eligible snippets

    \n+
    \n

    \n YASnippet does quite a bit of filtering to find out which snippets are\n eligible for expanding at the current cursor position.\n

    \n \n

    \n In particular, the following things matter:\n@@ -543,24 +543,24 @@\n Buffer-local yas-buffer-local-condition variable\n

    \n \n

    \n This variable provides finer grained control over what snippets can\n be expanded in the current buffer. For example, the constant\n yas-not-string-or-comment-condition has a value that disables\n-snippet expansion inside comments or string literals. See the\n+snippet expansion inside comments or string literals. See the\n condition system for more info.\n

    \n \n
    \n
    \n \n-
    \n-

    The condition system

    \n-
    \n+
    \n+

    The condition system

    \n+
    \n

    \n Consider this scenario: you are an old Emacs hacker. You like the\n abbrev-way and bind yas-expand to SPC. However, you don't want\n if to be expanded as a snippet when you are typing in a comment\n block or a string (e.g. in python-mode).\n

    \n \n@@ -598,19 +598,19 @@\n

    \n For the full set of possible conditions, see the documentation for\n yas-buffer-local-condition.\n

    \n
    \n
    \n \n-
    \n-

    Multiples snippet with the same key

    \n-
    \n+
    \n+

    Multiples snippet with the same key

    \n+
    \n

    \n-The rules outlined above can return more than\n+The rules outlined above can return more than\n one snippet to be expanded at point.\n

    \n \n

    \n When there are multiple candidates, YASnippet will let you select one.\n The UI for selecting multiple candidate can be customized through\n yas-prompt-functions , which defines your preferred methods of being\n@@ -629,19 +629,19 @@\n

    \n \n

    \n Currently there are some alternatives solution with YASnippet.\n

    \n
    \n \n-
    \n-

    Use the X window system

    \n-
    \n+
    \n+

    Use the X window system

    \n+
    \n \n-
    \n+
    \n

    \"x-menu.png\"\n

    \n
    \n \n

    \n The function yas-x-prompt can be used to show a popup menu for you to\n select. This menu will be part of you native window system widget, which\n@@ -654,36 +654,36 @@\n

  • Your window system may or may not allow to you use C-n, C-p to\n navigate this menu.
    • \n
  • This function can't be used when in a terminal.
    • \n \n
    \n
    \n \n-
    \n-

    Minibuffer prompting

    \n-
    \n+
    \n+

    Minibuffer prompting

    \n+
    \n \n-
    \n+
    \n

    \"ido-menu.png\"\n

    \n
    \n \n

    \n You can use functions yas-completing-prompt for the classic emacs\n completion method or yas-ido-prompt for a much nicer looking method.\n The best way is to try it. This works in a terminal.\n

    \n
    \n
    \n \n-
    \n-

    Use dropdown-menu.el

    \n-
    \n+
    \n+

    Use dropdown-menu.el

    \n+
    \n \n-
    \n+
    \n

    \"dropdown-menu.png\"\n

    \n
    \n \n

    \n The function yas-dropdown-prompt can also be placed in the\n yas-prompt-functions list.\n@@ -693,17 +693,17 @@\n This works in both window system and terminal and is customizable, you\n can use C-n, C-p to navigate, q to quit and even press 6 as a\n shortcut to select the 6th candidate.\n

    \n
    \n
    \n \n-
    \n-

    Roll your own

    \n-
    \n+
    \n+

    Roll your own

    \n+
    \n

    \n See the documentation on variable yas-prompt-functions\n

    \n
    \n
    \n
    \n
    \n"}, {"source1": "./usr/share/doc/elpa-yasnippet/html/snippet-menu.html", "source2": "./usr/share/doc/elpa-yasnippet/html/snippet-menu.html", "unified_diff": "@@ -214,19 +214,19 @@\n
    \n
    \n

    YASnippet menu

    \n \n

    \n When yas-minor-mode is active, YASnippet will setup a menu just after\n the \"Buffers\" menu in the menubar.\n

    \n@@ -244,38 +244,38 @@\n snippet definitions.\n \n
  • A series of submenus for customizing and exploring YASnippet\n behavior.
    • \n \n \n \n-
    \n+
    \n

    \"menu-1.png\"\n

    \n
    \n \n-
    \n-

    Loading snippets from menu

    \n-
    \n+
    \n+

    Loading snippets from menu

    \n+
    \n

    \n Invoking \"Load snippets…\" from the menu invokes yas-load-directory\n and prompts you for a snippet directory hierarchy to load.\n

    \n \n

    \n Also useful is the \"Reload everything\" item to invoke yas-reload-all\n which uncondionally reloads all the snippets directories defined in\n yas-snippet-dirs and rebuilds the menus.\n

    \n
    \n
    \n \n-
    \n-

    Snippet menu behavior

    \n-
    \n+
    \n+

    Snippet menu behavior

    \n+
    \n

    \n YASnippet will list in this section all the loaded snippet definitions\n organized by snippet table name.\n

    \n \n

    \n You can use this section to explore currently loaded snippets. If you\n@@ -303,38 +303,38 @@\n

    \n These customizations can also be found in the menu itself, under the\n \"Snippet menu behavior\" submenu.\n

    \n
    \n
    \n \n-
    \n-

    Controlling indenting

    \n-
    \n+
    \n+

    Controlling indenting

    \n+
    \n

    \n The \"Indenting\" submenu contains options to control the values of\n yas-indent-line and yas-also-auto-indent-first-line. See\n Writing snippets.\n

    \n
    \n
    \n \n-
    \n-

    Prompting method

    \n-
    \n+
    \n+

    Prompting method

    \n+
    \n

    \n The \"Prompting method\" submenu contains options to control the value of\n yas-prompt-functions. See Expanding snippets.\n

    \n
    \n
    \n \n-
    \n-

    Misc

    \n-
    \n+
    \n+

    Misc

    \n+
    \n

    \n The \"Misc\" submenu contains options to control the values of more\n variables.\n

    \n
    \n
    \n
    \n"}, {"source1": "./usr/share/doc/elpa-yasnippet/html/snippet-organization.html", "source2": "./usr/share/doc/elpa-yasnippet/html/snippet-organization.html", "unified_diff": "@@ -214,35 +214,35 @@\n
    \n
    \n

    Organizing snippets

    \n \n \n-
    \n-

    Basic structure

    \n-
    \n+
    \n+

    Basic structure

    \n+
    \n

    \n Snippet collections can be stored in plain text files. They are\n arranged by sub-directories naming snippet tables. These mostly\n name Emacs major mode names.\n

    \n \n-
    \n+
    \n .\n |-- c-mode\n |   `-- printf\n |-- java-mode\n |   `-- println\n `-- text-mode\n     |-- email\n@@ -253,17 +253,17 @@\n The collections are loaded into snippet tables which the\n triggering mechanism (see Expanding Snippets) looks up and\n (hopefully) causes the right snippet to be expanded for you.\n 
    \n
    \n
    \n \n-
    \n-

    Setting up yas-snippet-dirs

    \n-
    \n+
    \n+

    Setting up yas-snippet-dirs

    \n+
    \n

    \n The emacs variable yas-snippet-dirs tells YASnippet\n which collections to consider. It's used when you activate\n yas-global-mode or call\n yas-reload-all interactively.\n

    \n \n@@ -297,26 +297,26 @@\n Collections appearing earlier in the list override snippets with same names\n appearing in collections later in the list. yas-new-snippet always stores\n snippets in the first collection.\n

    \n
    \n
    \n \n-
    \n-

    The .yas-parents file

    \n-
    \n+
    \n+

    The .yas-parents file

    \n+
    \n

    \n It's very useful to have certain modes share snippets between\n themselves. To do this, choose a mode subdirectory and place a\n .yas-parents containing a whitespace-separated list of other mode\n names. When you reload those modes become parents of the original\n mode.\n

    \n \n-
    \n+
    \n .\n |-- c-mode\n |   |-- .yas-parents    # contains \"cc-mode text-mode\"\n |   `-- printf\n |-- cc-mode\n |   |-- for\n |   `-- while\n@@ -327,36 +327,36 @@\n     |-- email\n     `-- time\n 
    \n
    \n
    \n \n \n-
    \n-

    TODO The .yas-make-groups file

    \n-
    \n+
    \n+

    TODO The .yas-make-groups file

    \n+
    \n

    \n If you place an empty plain text file .yas-make-groups inside one\n of the mode directories, the names of these sub-directories are\n considered groups of snippets and the menu is organized much more\n cleanly:\n

    \n \n \n-
    \n+
    \n

    \"menu-groups.png\"\n

    \n
    \n \n

    \n Another way to achieve this is to place a # group: directive\n inside the snippet definition. See Writing Snippets.\n

    \n \n-
    \n+
    \n $ tree ruby-mode/\n ruby-mode/\n |-- .yas-make-groups\n |-- collections\n |   |-- each\n |   `-- ...\n |-- control structure\n@@ -371,28 +371,28 @@\n 
    \n Yet another way to create a nice snippet menu is to write into\n .yas-make-groups a menu definition. TODO\n 
    \n
    \n
    \n \n-
    \n-

    The .yas-setup.el file

    \n-
    \n+
    \n+

    The .yas-setup.el file

    \n+
    \n

    \n If there is file named .yas-setup.el in a mode's snippet\n subdirectory, it is loaded along with the snippets. Utility\n functions used by the snippets can be put here.\n

    \n
    \n
    \n \n-
    \n-

    The .yas-compiled-snippet.el file

    \n-
    \n+
    \n+

    The .yas-compiled-snippet.el file

    \n+
    \n

    \n You may compile a top-level snippet directory with the\n yas-compile-directory function, which will create a\n .yas-compiled-snippets.el file under each mode subdirectory,\n which contains definitions for all snippets in the subdirectory.\n Compilation helps improve loading time.\n

    \n@@ -400,17 +400,17 @@\n

    \n Alternatively, you may compile all directories in the list\n yas-snippet-dirs with the yas-recompile-all function.\n

    \n
    \n
    \n \n-
    \n-

    The .yas-skip file

    \n-
    \n+
    \n+

    The .yas-skip file

    \n+
    \n

    \n A .yas-skip file in a mode's snippet subdirectory tells YASnippet\n not to load snippets from there.\n

    \n
    \n
    \n
    \n"}, {"source1": "./usr/share/doc/elpa-yasnippet/html/snippet-reference.html", "source2": "./usr/share/doc/elpa-yasnippet/html/snippet-reference.html", "unified_diff": "@@ -214,15 +214,15 @@\n
    \n
    \n

    Reference

    \n
    \n

    Table of Contents

    \n \n
    \n \n-
    \n-

    Interactive functions

    \n-
    \n+
    \n+

    Interactive functions

    \n+
    \n
    \n
    \n

    yas-visit-snippet-file ()

    \n
    \n

    \n Choose a snippet to edit, selection like yas-insert-snippet.\n

    \n@@ -561,15 +561,15 @@\n positive prefix argument turns on the mode.\n Negative prefix argument turns off the mode.\n

    \n \n

    \n Key bindings:\n

    \n-
    \n+
    \n \n Key             Binding\n -------------------------------------------------------------------------------\n C-c & C-n\tyas-new-snippet\n C-c & C-s\tyas-insert-snippet\n C-c & C-v\tyas-visit-snippet-file\n 
    \n@@ -791,17 +791,17 @@\n 
    \n 
    \n warning: no doc for symbol yas-abort-snippet\n 
    \n 
    \n
    \n
    \n-
    \n-

    Customization variables

    \n-
    \n+
    \n+

    Customization variables

    \n+
    \n
    \n
    \n

    yas-choose-keys-first

    \n
    \n

    \n If non-nil, prompt for snippet key first, then for template.\n

    \n@@ -1219,17 +1219,17 @@\n \n

    \n Naturally this is only valid when yas-indent-line is auto.\n

    \n
    \n
    \n
    \n-
    \n-

    Useful functions

    \n-
    \n+
    \n+

    Useful functions

    \n+
    \n
    \n
    \n

    yas-global-mode-check-buffers ()

    \n
    \n

    \n warning: no doc for symbol yas-global-mode-check-buffers\n

    \n@@ -1743,17 +1743,17 @@\n
    \n

    \n Display choices in a x-window prompt.\n

    \n
    \n
    \n
    \n-
    \n-

    Useful variables

    \n-
    \n+
    \n+

    Useful variables

    \n+
    \n
    \n
    \n

    yas-snippet-end

    \n
    \n

    \n End position of the last snippet committed.\n

    \n"}]}]}]}]}