From: Lars Ingebrigtsen <larsi@gnus.org>
To: "Etienne Prud'homme" <e.e.f.prudhomme@gmail.com>
Cc: 26550@debbugs.gnu.org
Subject: bug#26550: [PATCH] Fix js.el filling inline JSDoc tags
Date: Mon, 24 Jun 2019 18:44:15 +0200 [thread overview]
Message-ID: <m31rzjrl0g.fsf@gnus.org> (raw)
In-Reply-To: <CAK0FJvvd1Rg9naWELj=F2Oo-fsXUEO9o5vkd9W=FDOAQ4m_UBw@mail.gmail.com> (Etienne Prud'homme's message of "Tue, 18 Apr 2017 00:18:11 -0400")
"Etienne Prud'homme" <e.e.f.prudhomme@gmail.com> writes:
> However, the link tag can be broken arbitrary and would make the tag harder
> to read (without considering font-lock that is implemented in an other
> package).
>
>> /**
>> * @foo
>> * Description. Link to other symbol {@link
>> * document.body.style}
>> * @bar
>
> I searched the JSDoc documentation[1] about line breaks inside an inline
> tags and didn't find explicit information about whether or not it was valid.
> Given that inline litterally means on one line, I guess we can pretend the
> specification doesn't allow line breaks inside an inline tag.
[...]
> After checking the code, it seems that having a newline inside the inline tag
> is valid [1].
Given this, the proposed change may not be the right one, so I'm closing
this bug report.
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
prev parent reply other threads:[~2019-06-24 16:44 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-18 4:18 bug#26550: [PATCH] Fix js.el filling inline JSDoc tags Etienne Prud'homme
2017-04-18 16:14 ` bug#26550: Etienne Prud'homme
2017-04-20 0:32 ` bug#26550: Etienne Prud'homme
2019-06-24 16:44 ` Lars Ingebrigtsen [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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=m31rzjrl0g.fsf@gnus.org \
--to=larsi@gnus.org \
--cc=26550@debbugs.gnu.org \
--cc=e.e.f.prudhomme@gmail.com \
/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 public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).