all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Stefan Kangas <stefankangas@gmail.com>
To: Yuan Fu <casouri@gmail.com>
Cc: mr.meowking@anche.no, Eli Zaretskii <eliz@gnu.org>,
	70017@debbugs.gnu.org, 70016@debbugs.gnu.org
Subject: bug#70016: bug#70017: Emacs 29.3 treesit-parser-list function parameters changed, while the master branch didn't
Date: Sat, 29 Jun 2024 22:56:49 -0700	[thread overview]
Message-ID: <CADwFkmm4mGN6cQUCW+kSWMSUM4jgKpf6Fn8+LcOq_eq1ii7LXQ@mail.gmail.com> (raw)
In-Reply-To: <83D02CA6-A7E5-413B-B813-809E3E8E3499@gmail.com> (Yuan Fu's message of "Sun, 7 Apr 2024 23:29:34 -0700")

Yuan Fu <casouri@gmail.com> writes:

> My pleasure. It just happens today I finally got a day where I can sit down and
> write some code. I updated manual and news entries. There’s one thing though, I
> couldn’t find a good way to avoid using variables (which starts with lowercase)
> at the beginning of sentences. I don’t know how do you feel about having lower
> case letter at the beginning of sentences. If you have good tips on avoiding
> them I’m happy to apply it to all the occurrences in the new manual entries I
> wrote.

My best idea for that is to reformulate the sentence.  It's not the end
of the world, IMHO.

Could this bug be closed?





  reply	other threads:[~2024-06-30  5:56 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-26  3:23 bug#70016: Emacs 29.3 treesit-parser-list function parameters differ from the master branch Meow King via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-03-26 19:25 ` Eli Zaretskii
2024-03-28  4:47   ` Yuan Fu
2024-04-06  9:17     ` Eli Zaretskii
2024-04-08  6:29       ` Yuan Fu
2024-06-30  5:56         ` Stefan Kangas [this message]
2024-07-01  4:54           ` bug#70017: Emacs 29.3 treesit-parser-list function parameters changed, while the master branch didn't Yuan Fu

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=CADwFkmm4mGN6cQUCW+kSWMSUM4jgKpf6Fn8+LcOq_eq1ii7LXQ@mail.gmail.com \
    --to=stefankangas@gmail.com \
    --cc=70016@debbugs.gnu.org \
    --cc=70017@debbugs.gnu.org \
    --cc=casouri@gmail.com \
    --cc=eliz@gnu.org \
    --cc=mr.meowking@anche.no \
    /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.