emacs-bug-tracker
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

bug#60317: closed (29.0.50; lispref/text.texi has multiple names for sql


From: GNU bug Tracking System
Subject: bug#60317: closed (29.0.50; lispref/text.texi has multiple names for sqlite-select argument)
Date: Sun, 25 Dec 2022 17:45:02 +0000

Your message dated Sun, 25 Dec 2022 19:44:53 +0200
with message-id <83r0wn2x9m.fsf@gnu.org>
and subject line Re: bug#60317: 29.0.50; lispref/text.texi has multiple names 
for sqlite-select argument
has caused the debbugs.gnu.org bug report #60317,
regarding 29.0.50; lispref/text.texi has multiple names for sqlite-select 
argument
to be marked as done.

(If you believe you have received this mail in error, please contact
help-debbugs@gnu.org.)


-- 
60317: https://debbugs.gnu.org/cgi/bugreport.cgi?bug=60317
GNU Bug Tracking System
Contact help-debbugs@gnu.org with problems
--- Begin Message --- Subject: 29.0.50; lispref/text.texi has multiple names for sqlite-select argument Date: Sun, 25 Dec 2022 11:28:50 -0600 User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:91.0) Gecko/20100101 Thunderbird/91.6.1
Hi,

I just noticed a small mistake in lispref/text.texi in the emacs-29 branch: the documentation for the `sqlite-select' function names its second optional argument `result-type', but in the subsequent paragraphs it's named `return-type'. I'm not sure which is preferred, so I haven't prepared a patch.

Thanks,
Adam



--- End Message ---
--- Begin Message --- Subject: Re: bug#60317: 29.0.50; lispref/text.texi has multiple names for sqlite-select argument Date: Sun, 25 Dec 2022 19:44:53 +0200
> Date: Sun, 25 Dec 2022 11:28:50 -0600
> From: Adam Porter <adam@alphapapa.net>
> 
> I just noticed a small mistake in lispref/text.texi in the emacs-29 
> branch: the documentation for the `sqlite-select' function names its 
> second optional argument `result-type', but in the subsequent paragraphs 
> it's named `return-type'.  I'm not sure which is preferred, so I haven't 
> prepared a patch.

Thanks, fixed.  ("return-type" is correct, since it's consistent with
the doc string.)


--- End Message ---

reply via email to

[Prev in Thread] Current Thread [Next in Thread]