update packages

lisp/ivy/ivy.info

@@ -1,4 +1,4 @@
-This is ivy.info, produced by makeinfo version 6.8 from ivy.texi.
+This is ivy.info, produced by makeinfo version 7.1.1 from ivy.texi.
 
 Ivy manual, version 0.15.0
 
@@ -11,7 +11,7 @@ available choices while previewing in the minibuffer.  Selecting the
 final candidate is either through simple keyboard character inputs or
 through powerful regular expressions.
 
-   Copyright (C) 2015–2025 Free Software Foundation, Inc.
+   Copyright (C) 2015-2025 Free Software Foundation, Inc.
 
      Permission is granted to copy, distribute and/or modify this
      document under the terms of the GNU Free Documentation License,
@@ -44,7 +44,7 @@ Ivy User Manual
 * Variable Index::
 * Keystroke Index::
 
-— The Detailed Node Listing —
+-- The Detailed Node Listing --
 
 Installation
 
@@ -144,11 +144,11 @@ Minimalism
 Simplicity
 ..........
 
-     Simplicity is about Ivy’s behavior in the minibuffer.  It is also
-     about the code interface to extend Ivy’s functionality.  The
+     Simplicity is about Ivy's behavior in the minibuffer.  It is also
+     about the code interface to extend Ivy's functionality.  The
      minibuffer area behaves as close to ‘fundamental-mode’ as possible.
      ‘SPC’ inserts a space, for example, instead of being bound to the
-     more complex ‘minibuffer-complete-word’.  Ivy’s code uses
+     more complex ‘minibuffer-complete-word’.  Ivy's code uses
      easy-to-examine global variables; avoids needless complications
      with branch-introducing custom macros.
 
@@ -163,7 +163,7 @@ Customizability
      ‘ivy-format-functions-alist’).  Or take the customization of
      actions, say after the candidate function is selected.  ‘RET’ uses
      ‘counsel-describe-function’ to describe the function, whereas ‘M-o
-     d’ jumps to that function’s definition in the code.  The ‘M-o’
+     d’ jumps to that function's definition in the code.  The ‘M-o’
      prefix can be uniformly used with characters like ‘d’ to group
      similar actions.
 
@@ -185,8 +185,8 @@ File: ivy.info,  Node: Installation,  Next: Getting started,  Prev: Introduction
 2 Installation
 **************
 
-Install Ivy automatically through Emacs’s package manager, or manually
-from Ivy’s development repository.
+Install Ivy automatically through Emacs's package manager, or manually
+from Ivy's development repository.
 
    Emacs 24.5 is the oldest version to run Ivy.
 
@@ -236,7 +236,7 @@ Why install from Git?
 
         • No need to wait for GNU ELPA / MELPA builds
         • Easy to revert to previous versions
-        • Contribute to Ivy’s development; send patches; pull requests
+        • Contribute to Ivy's development; send patches; pull requests
 
 Configuration steps
 ...................
@@ -285,7 +285,7 @@ Here are some basic settings particularly useful for new Ivy users:
 
    If you want, you can go without any customizations at all.  The above
 settings are the most bang for the buck in terms of customization.  So
-users that typically don’t like customize a lot are advised to look at
+users that typically don't like customize a lot are advised to look at
 these settings first.
 
    For more advanced customizations, refer to ‘M-x describe-variable’
@@ -472,7 +472,7 @@ extends usability of lists in Emacs.
 
      This is useful e.g.  when you call ‘find-file’ to create a new
      file, but the desired name matches an existing file.  In that case,
-     using ‘C-j’ would select that existing file, which isn’t what you
+     using ‘C-j’ would select that existing file, which isn't what you
      want - use this command instead.
 
 ‘C-'’ (‘ivy-avy’)
@@ -594,7 +594,7 @@ File: ivy.info,  Node: Key bindings that alter the minibuffer input,  Next: Othe
 ‘C-r’ (‘ivy-reverse-i-search’)
 ..............................
 
-     Starts a recursive completion session through the command’s
+     Starts a recursive completion session through the command's
      history.
 
      This works just like ‘C-r’ at the bash command prompt, where the
@@ -757,7 +757,7 @@ File: ivy.info,  Node: Completion Styles,  Next: Customization,  Prev: Key bindi
 5 Completion Styles
 *******************
 
-Ivy’s completion functions rely on a regex builder - a function that
+Ivy's completion functions rely on a regex builder - a function that
 transforms a string input to a string regex.  All current candidates
 simply have to match this regex.  Each collection can be assigned its
 own regex builder by customizing ‘ivy-re-builders-alist’.
@@ -770,7 +770,7 @@ of the following:
    • ‘ivy--regex-fuzzy’
    • ‘regexp-quote’
 
-   A catch-all key, ‘t’, applies to all collections that don’t have
+   A catch-all key, ‘t’, applies to all collections that don't have
 their own key.
 
    The default is:
@@ -807,15 +807,15 @@ second argument to ‘completing-read’ for file name completion.
 
 File: ivy.info,  Node: ivy--regex-plus,  Next: ivy--regex-ignore-order,  Up: Completion Styles
 
-5.1 ivy–regex-plus
+5.1 ivy-regex-plus
 ==================
 
-‘ivy--regex-plus’ is Ivy’s default completion method.
+‘ivy--regex-plus’ is Ivy's default completion method.
 
    ‘ivy--regex-plus’ matches by splitting the input by spaces and
 rebuilding it into a regex.
 
-   As the search string is typed in Ivy’s minibuffer, it is transformed
+   As the search string is typed in Ivy's minibuffer, it is transformed
 into valid regex syntax.  If the string is ‘"for example"’, it is
 transformed into
 
@@ -844,7 +844,7 @@ of a negation group.
 
 File: ivy.info,  Node: ivy--regex-ignore-order,  Next: ivy--regex-fuzzy,  Prev: ivy--regex-plus,  Up: Completion Styles
 
-5.2 ivy–regex-ignore-order
+5.2 ivy-regex-ignore-order
 ==========================
 
 ‘ivy--regex-ignore-order’ ignores the order of regexp tokens when
@@ -854,13 +854,13 @@ example"’ will match ‘"example test for"’.
 
 File: ivy.info,  Node: ivy--regex-fuzzy,  Prev: ivy--regex-ignore-order,  Up: Completion Styles
 
-5.3 ivy–regex-fuzzy
+5.3 ivy-regex-fuzzy
 ===================
 
 ‘ivy--regex-fuzzy’ splits each character with a wild card.  Searching
 for ‘"for"’ returns all ‘"f.*o.*r"’ matches, resulting in a large number
 of hits.  Yet some searches need these extra hits.  Ivy sorts such large
-lists using ‘flx’ package’s scoring mechanism, if it’s installed.
+lists using ‘flx’ package's scoring mechanism, if it's installed.
 
    ‘C-o m’ toggles the current regexp builder.
 
@@ -1011,7 +1011,7 @@ File: ivy.info,  Node: Defcustoms,  Next: Actions,  Prev: Faces,  Up: Customizat
      This is usually the case when there is no text left to delete,
      i.e., when ‘DEL’ is typed at the beginning of the minibuffer.
 
-     The default behavior is to quit the completion after ‘DEL’ – a
+     The default behavior is to quit the completion after ‘DEL’ - a
      handy key to invoke after mistakenly triggering a completion.
 
      Another common option is ‘ignore’, which does nothing.
@@ -1448,7 +1448,7 @@ File: ivy.info,  Node: Optional arguments for ivy-read,  Next: Example - counsel
 ...........
 
      Is a function to filter the initial collection.  It has to be
-     compatible with ‘all-completions’.  Tip: most of the time, it’s
+     compatible with ‘all-completions’.  Tip: most of the time, it's
      simpler to just apply this filter to the ‘collection’ argument
      itself, e.g.  ‘(cl-remove-if-not predicate collection)’.
 
@@ -1464,7 +1464,7 @@ File: ivy.info,  Node: Optional arguments for ivy-read,  Next: Example - counsel
      This string argument is included for compatibility with
      ‘completing-read’, which inserts it into the minibuffer.
 
-     It’s recommended to use the ‘preselect’ argument instead of this.
+     It's recommended to use the ‘preselect’ argument instead of this.
 
 ‘history’
 .........
@@ -1498,7 +1498,7 @@ File: ivy.info,  Node: Optional arguments for ivy-read,  Next: Example - counsel
 ...........
 
      Is the function called each time the current candidate changes.
-     This function takes no arguments and is called in the minibuffer’s
+     This function takes no arguments and is called in the minibuffer's
      ‘post-command-hook’.  See ‘swiper’ for an example usage.
 
 ‘sort’
@@ -1563,7 +1563,7 @@ the rest of the arguments are for fine-tuning, and could be omitted.
 
    The ‘action’ argument could also be omitted - but then ‘ivy-read’
 would do nothing except returning the string result, which you could
-later use yourself.  However, it’s recommended that you use the ‘action’
+later use yourself.  However, it's recommended that you use the ‘action’
 argument.
 
      (defun counsel-describe-function ()
@@ -1599,14 +1599,14 @@ that they appear:
      input is necessary.
    • The ‘history’ argument is for keeping the history of this command
      separate from the common history in ‘ivy-history’.
-   • The ‘require-match’ is set to ‘t’ since it doesn’t make sense to
+   • The ‘require-match’ is set to ‘t’ since it doesn't make sense to
      call ‘describe-function’ on an un-interned symbol.
    • The ‘action’ argument calls ‘describe-function’ on the interned
      selected candidate.
    • The ‘caller’ argument identifies this completion session.  This is
      important, since with the collection being a list of strings and
      not a function name, the only other way for ‘ivy-read’ to identify
-     "who’s calling" and to apply the appropriate customizations is to
+     "who's calling" and to apply the appropriate customizations is to
      examine ‘this-command’.  But ‘this-command’ would be modified if
      another command called ‘counsel-describe-function’.
 
@@ -1665,8 +1665,8 @@ narrowing) or select a candidate from the visible collection.
 order that they appear:
 
    • ‘counsel-locate-function’ takes a string argument and returns a
-     list of strings.  Note that it’s not compatible with
-     ‘all-completions’, but since we’re not using that here, might as
+     list of strings.  Note that it's not compatible with
+     ‘all-completions’, but since we're not using that here, might as
      well use one argument instead of three.
    • ‘ivy-more-chars’ is a simple function that returns e.g.  ‘'("2
      chars more")’ asking the user for more input.
@@ -1917,52 +1917,52 @@ File: ivy.info,  Node: Keystroke Index,  Prev: Variable Index,  Up: Top
 
 Tag Table:
 Node: Top1192
-Node: Introduction3103
-Node: Installation5626
-Node: Installing from Emacs Package Manager6002
-Node: Installing from the Git repository7249
-Node: Getting started8079
-Node: Basic customization8386
-Node: Key bindings8981
-Node: Global key bindings9173
-Node: Minibuffer key bindings11647
-Node: Key bindings for navigation12879
-Node: Key bindings for single selection action then exit minibuffer14086
-Node: Key bindings for multiple selections and actions keep minibuffer open16770
-Node: Key bindings that alter the minibuffer input19391
-Node: Other key bindings21338
-Node: Hydra in the minibuffer21716
-Node: Saving the current completion session to a buffer24134
-Node: Completion Styles25546
-Node: ivy--regex-plus27304
-Node: ivy--regex-ignore-order28790
-Node: ivy--regex-fuzzy29158
-Node: Customization29655
-Node: Faces29841
-Node: Defcustoms32270
-Node: Actions33596
-Node: What are actions?33922
-Node: How can different actions be called?34740
-Node: How to modify the actions list?35311
-Node: Example - add two actions to each command35971
-Node: How to undo adding the two actions36930
-Node: How to add actions to a specific command37382
-Node: Example - define a new command with several actions37798
-Node: Test the above function with ivy-occur38735
-Node: Packages39577
-Node: Commands40542
-Node: File Name Completion40727
-Node: Using TRAMP42684
-Node: Buffer Name Completion44186
-Node: Counsel commands44801
-Node: API45448
-Node: Required arguments for ivy-read46046
-Node: Optional arguments for ivy-read46565
-Node: Example - counsel-describe-function49991
-Node: Example - counsel-locate52975
-Node: Example - ivy-read-with-extra-properties56844
-Node: Variable Index58122
-Node: Keystroke Index65246
+Node: Introduction3101
+Node: Installation5616
+Node: Installing from Emacs Package Manager5988
+Node: Installing from the Git repository7235
+Node: Getting started8063
+Node: Basic customization8370
+Node: Key bindings8963
+Node: Global key bindings9155
+Node: Minibuffer key bindings11629
+Node: Key bindings for navigation12861
+Node: Key bindings for single selection action then exit minibuffer14068
+Node: Key bindings for multiple selections and actions keep minibuffer open16750
+Node: Key bindings that alter the minibuffer input19371
+Node: Other key bindings21316
+Node: Hydra in the minibuffer21694
+Node: Saving the current completion session to a buffer24112
+Node: Completion Styles25524
+Node: ivy--regex-plus27278
+Node: ivy--regex-ignore-order28758
+Node: ivy--regex-fuzzy29124
+Node: Customization29615
+Node: Faces29801
+Node: Defcustoms32230
+Node: Actions33554
+Node: What are actions?33880
+Node: How can different actions be called?34698
+Node: How to modify the actions list?35269
+Node: Example - add two actions to each command35929
+Node: How to undo adding the two actions36888
+Node: How to add actions to a specific command37340
+Node: Example - define a new command with several actions37756
+Node: Test the above function with ivy-occur38693
+Node: Packages39535
+Node: Commands40500
+Node: File Name Completion40685
+Node: Using TRAMP42642
+Node: Buffer Name Completion44144
+Node: Counsel commands44759
+Node: API45406
+Node: Required arguments for ivy-read46004
+Node: Optional arguments for ivy-read46523
+Node: Example - counsel-describe-function49943
+Node: Example - counsel-locate52921
+Node: Example - ivy-read-with-extra-properties56786
+Node: Variable Index58064
+Node: Keystroke Index65188
 
 End Tag Table