From: Brian Inglis <Brian.Inglis@Shaw.ca>
To: cygwin@cygwin.com
Subject: Re: intelligent following of directions, or following them by rote...
Date: Sat, 08 Oct 2016 18:45:00 -0000 [thread overview]
Message-ID: <ed28bb65-8072-608e-56a5-d536433cdf4d@Shaw.ca> (raw)
In-Reply-To: <57F81BD9.8090502@tlinx.org>
On 2016-10-07 16:04, Linda Walsh wrote:
> Andrey Repin wrote:
>> Greetings, Linda Walsh!
>>> Achim Gratz wrote:
>>>> Now, that last question of yours: No, the package manager should never
>>>> allow you to not install a base package. These are in category "Base"
>>>> precisely so the rest of the system can rely on the functionality
>>>> provided.
>>> But back to the 1st Q. What other programs will fail to work
>>> if the base-version of vim isn't installed?
>> The question is not about vim...
> But it is about vim. That's the package the user wanted to
> install their own version of.
> Anyway, thinking about what you are doing and why things are
> they way they are, is important -- which is why I asked, what affect
> on the cygwin installation would be if you didn't install the base
> vim package? If you don't know the answer, then maybe the defaults
> are for you, but if you have an idea of what vim does and how it might
> be used to run the rest of cygwin, then you might experiment to find
> if things fail or continue to work w/o the base-vim. Just a thought.
Type v inside a PAGER (e.g. less or more).
Run an editor on the current (long) command line in readline or shell history.
Edit a commit message in any VCS.
Edit crontab entries.
You can change some of these if you prefer ed or emacs (EDITOR, VISUAL),
and ex is a symlink to vi (vim-minimal).
--
Take care. Thanks, Brian Inglis, Calgary, Alberta, Canada
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
next prev parent reply other threads:[~2016-10-08 15:14 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-06 17:15 Blocking a base package from installing Chris Sutcliffe
2016-10-06 17:28 ` Hans-Bernhard Bröker
2016-10-06 17:37 ` Achim Gratz
2016-10-06 18:30 ` Linda Walsh
2016-10-06 18:35 ` Eric Blake
2016-10-06 19:15 ` Achim Gratz
2016-10-07 0:16 ` Linda Walsh
2016-10-07 11:04 ` Andrey Repin
2016-10-07 22:40 ` intelligent following of directions, or following them by rote Linda Walsh
2016-10-08 18:45 ` Brian Inglis [this message]
2016-10-09 6:56 ` Linda Walsh
2016-10-09 4:35 ` Erik Soderquist
2016-10-09 8:55 ` Linda Walsh
2016-10-07 22:04 ` Blocking a base package from installing Hans-Bernhard Bröker
2016-10-08 14:45 ` Linda Walsh
2016-10-06 19:02 ` Andrey Repin
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=ed28bb65-8072-608e-56a5-d536433cdf4d@Shaw.ca \
--to=brian.inglis@shaw.ca \
--cc=cygwin@cygwin.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.
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).