all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: ludvig-faddeev@gmx.com
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: 48768@debbugs.gnu.org
Subject: bug#48768: Introducing ability to append to docstring
Date: Tue, 1 Jun 2021 18:03:36 +0200	[thread overview]
Message-ID: <trinity-0087a00b-59fc-4704-a678-7dae46be7e2f-1622563416119@3c-app-mailcom-bs01> (raw)
In-Reply-To: <87r1hlbnrf.fsf@gnus.org>



> Sent: Wednesday, June 02, 2021 at 3:36 AM
> From: "Lars Ingebrigtsen" <larsi@gnus.org>
> To: ludvig-faddeev@gmx.com
> Cc: 48768@debbugs.gnu.org
> Subject: Re: bug#48768: Introducing ability to append to docstring
>
> ludvig-faddeev@gmx.com writes:
>
> > A useful capability would allow one to append to a defun docstring
> > using a defvar.
> >
> > User could write a brief description for the docstring, and later
> > append more details
> > from a defvar.
>
> I do not think that would be a useful interface -- you can append and
> change doc strings all you want by manipulating the
> `function-documentation' property.
>
> So I'm closing this bug report.

If you can tell me how to append, I can use that, but currently, what people
have said do not work.

So appending to a doc-string is not useful.  Appending to a string is the most
useful thing there is !

> --
> (domestic pets only, the antidote for overdose, milk.)
>    bloggy blog: http://lars.ingebrigtsen.no
>





      reply	other threads:[~2021-06-01 16:03 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-01  0:07 bug#48768: Introducing ability to append to docstring ludvig-faddeev
2021-06-01  4:53 ` Richard Stallman
2021-06-01 14:08   ` Michael Heerdegen
2021-06-01 14:44     ` bug#48768: [External] : " Drew Adams
2021-06-01 15:36 ` Lars Ingebrigtsen
2021-06-01 16:03   ` ludvig-faddeev [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=trinity-0087a00b-59fc-4704-a678-7dae46be7e2f-1622563416119@3c-app-mailcom-bs01 \
    --to=ludvig-faddeev@gmx.com \
    --cc=48768@debbugs.gnu.org \
    --cc=larsi@gnus.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.