From: Jack Hill <jackhill@jackhill.us>
To: 39776@debbugs.gnu.org
Subject: bug#39776: Explain difference between vim and vim-full (feature request)
Date: Tue, 25 Feb 2020 00:44:30 -0500 (EST) [thread overview]
Message-ID: <alpine.DEB.2.20.2002250042140.19733@marsh.hcoop.net> (raw)
Hi Guix,
This is an enhancement request: I think we should explain what vim-full
provides over vim in the package description. What do you think?
All the best,
Jack
next reply other threads:[~2020-02-25 5:45 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-25 5:44 Jack Hill [this message]
2020-02-25 15:30 ` bug#39776: Explain difference between vim and vim-full (feature request) Leo Famulari
2020-02-25 16:32 ` Jack Hill
2020-02-25 19:16 ` bug#39776: [PATCH] gnu: vim-full: Describe differences from vim Jack Hill
2020-02-26 20:48 ` Marius Bakke
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://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=alpine.DEB.2.20.2002250042140.19733@marsh.hcoop.net \
--to=jackhill@jackhill.us \
--cc=39776@debbugs.gnu.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 public inbox
https://git.savannah.gnu.org/cgit/guix.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).