From: Oleg Pykhalov <go.wigust@gmail.com>
To: Christopher Baines <mail@cbaines.net>
Cc: 28830@debbugs.gnu.org, 28830-done@debbugs.gnu.org
Subject: bug#28830: [PATCH] gnu: Add emacs-ggtags.
Date: Tue, 31 Oct 2017 20:11:14 +0300 [thread overview]
Message-ID: <87fu9znsy5.fsf@gmail.com> (raw)
In-Reply-To: <20171031082218.2a45cfab@cbaines.net> (Christopher Baines's message of "Tue, 31 Oct 2017 08:22:18 +0000")
[-- Attachment #1: Type: text/plain, Size: 3331 bytes --]
Hello Christopher,
Christopher Baines <mail@cbaines.net> writes:
>> >> + (synopsis "Frontend to GNU Global source code tagging system")
>> >
>> > I'd suggest putting "the" in here, so "Frontend to the GNU Global ...",
>> > as I think that reads better.
>>
>> [...]
>>
>> > Similarly with "the GNU Global" in the description. What do you think?
>> > Apart from that, this looks fine to me :)
>>
>> I don't think so. Upstream¹ doesn't have an article “the” before GNU
>> Global, too. WDYT?
>>
>> ¹ http://elpa.gnu.org/packages/ggtags.html
>
> I don't think there is any harm in improving on the descriptions of the
> software from the upstream source. But I'll leave it up to you to make
> the decision.
>
> Unfortunately, I don't have a very formal understanding of English
> grammar, but there is some information about definite articles [1].
> Which I think says that its appropriate to use as there is one,
> specific "GNU Global source code tagging system".
>
> 1:
> https://learnenglish.britishcouncil.org/en/english-grammar/determiners-and-quantifiers/definite-article
OK if you fill it's more readable or elegant.
I also checked some installed packages on my system. It seems common to
use *the* before software name at least in package synopsis.
Accessing passwords from *the* GNOME keyring
Access *the* Debbugs bug tracker in Emacs
Adjust *the* color temperature of your screen
An implementation of *the* Domain Name System
BASH completion for *the* shell buffer
Client and server for *the* secure shell (ssh) protocol
Commands to start *the* X Window server
Copy directory to *the* gh-pages branch
Development manual pages from *the* Linux project
Discover key bindings for *the* current Emacs major mode
Emacs interface for *the* Git version control system
Free replacements for *the* PostScript fonts
Go to *the* last change in *the* Emacs buffer
Grabs *the* path to JSON values in a JSON file
Implementation of *the* Perl programming language
Lisp dialect running on *the* JVM
Locate files on *the* file system
Manage encryption keys and passwords in *the* GNOME keyring
Polish up poor writing on *the* fly
Recursively list *the* contents of a directory
Reddit backend for *the* Gnus newsreader
Reference manual for *the* C programming language
Set *the* keyboard using *the* X Keyboard Extension
Single-player, RPG roguelike game set in *the* world of Eyal
Suggest Elisp functions that give *the* output requested
Terminal emulator for *the*
TeX Live, a package of *the* TeX typesetting system
*The* extensible, customizable, self-documenting text editor
*The* Glasgow Haskell Compiler
*The* GNU debugger
*The* GNU documentation format
*The* OCaml programming language
*The* SQLite database management system
*The* standard Windows interoperability suite of programs for GNU and Unix
Translations from *the* command line
Utilities for *the* Advanced Linux Sound Architecture (ALSA)
Xorg implementation of *the* X Window System
Pushed as cd5c3979d18ca5bc5d32b9044330453c244df1a5
Thanks,
Oleg.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 832 bytes --]
next prev parent reply other threads:[~2017-10-31 17:12 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-14 9:04 [bug#28830] [PATCH] gnu: Add emacs-ggtags Oleg Pykhalov
2017-10-16 5:51 ` Christopher Baines
2017-10-16 10:22 ` Oleg Pykhalov
2017-10-31 8:22 ` Christopher Baines
2017-10-31 17:11 ` Oleg Pykhalov [this message]
2017-10-31 19:39 ` Tobias Geerinckx-Rice
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=87fu9znsy5.fsf@gmail.com \
--to=go.wigust@gmail.com \
--cc=28830-done@debbugs.gnu.org \
--cc=28830@debbugs.gnu.org \
--cc=mail@cbaines.net \
/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/guix.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.