[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[nongnu] elpa/geiser-guile 71a6be0043 3/3: fix: geiser-guile.texi re-gen
From: |
ELPA Syncer |
Subject: |
[nongnu] elpa/geiser-guile 71a6be0043 3/3: fix: geiser-guile.texi re-generated from readme.org |
Date: |
Thu, 14 Mar 2024 16:00:46 -0400 (EDT) |
branch: elpa/geiser-guile
commit 71a6be00433a157de3936f208c7a1bd0192b12cd
Author: jao <jao@gnu.org>
Commit: jao <jao@gnu.org>
fix: geiser-guile.texi re-generated from readme.org
---
geiser-guile.texi | 14 +++++++++-----
readme.org | 7 +++++++
2 files changed, 16 insertions(+), 5 deletions(-)
diff --git a/geiser-guile.texi b/geiser-guile.texi
index ae605abefd..8902a30c90 100644
--- a/geiser-guile.texi
+++ b/geiser-guile.texi
@@ -25,6 +25,7 @@
@menu
* Overview::
* Start up::
+* Texinfo docstrings::
* Debugging support::
* Tramp support::
@end menu
@@ -37,7 +38,7 @@ This package provides support for using
@uref{https://www.gnu.org/software/guile
Provided @uref{https://gitlab.com/emacs-geiser/geiser, geiser} is installed in
your system, if this package's
directory is in your load path, just add @code{(require 'geiser-guile)} to
-your initialisation files and then @code{M-x run-guile} to start a REPL@.
+your initialisation files and then @code{M-x geiser-guile} to start a REPL@.
Scheme files with a Guile module declaration should be automatically
recognised as Guile-flavoured Geiser buffers.
@@ -68,15 +69,18 @@ to disable loading the second. But there are subtle
differences
in the way Guile loads the initialization file versus how it loads
a file specified via the @samp{-l} flag. If what you want is just
loading @samp{~/.guile}, leave @code{geiser-guile-init-file} alone and set
-@code{geiser-guile-load-init-file-p} to @code{t} instead.
+@code{geiser-guile-load-init-file} to @code{t} instead.
One can also provide a global list of paths to add to Guile's
@samp{%load-path} via @code{geiser-guile-load-path}.
+@node Texinfo docstrings
+@unnumbered Texinfo docstrings
+
You can enable processing of texinfo in docstrings by customizing
-@code{geiser-guile-doc-process-texinfo} to a non-nil value. If
-enabled and docstring is a valid texinfo snippet, it will be converted
-into a plain text before being displayed.
+@code{geiser-guile-doc-process-texinfo} to a non-nil value. If enabled and
+docstring is a valid texinfo snippet, it will be converted into a plain text
+before being displayed.
@node Debugging support
@unnumbered Debugging support
diff --git a/readme.org b/readme.org
index 79e6fd952f..3b8a6ca542 100644
--- a/readme.org
+++ b/readme.org
@@ -47,6 +47,13 @@ geiser-guile.
One can also provide a global list of paths to add to Guile's
=%load-path= via ~geiser-guile-load-path~.
+* Texinfo docstrings
+
+ You can enable processing of texinfo in docstrings by customizing
+ ~geiser-guile-doc-process-texinfo~ to a non-nil value. If enabled and
+ docstring is a valid texinfo snippet, it will be converted into a plain text
+ before being displayed.
+
* Debugging support
Guile supports all the debugger commands supported by Geiser (it's