Re: A guide on setting up C/C++ development environment for Emacs

[Jai Dayal <dayalsoap@gmail.com>]

Actually, nope. When I decide to install an OS, say CentOS, I do not expect
to find a discussion on the pluses and minuses of CentOS on the
installation page. That's a completely different topic that has nothing to
do with CentOS installation.

Same with the actual Emacs page; on the installation section, there's no
discussion on the pluses and minuses of Emacs there in an attempt to avoid
having "disappointed people". When someone chooses to install something,
there's an understanding that they want to install it because they know
about it, or are wanting to try it out. Nobody with an IQ higher than 12
installs something for the first time, without reading about it, and
assumes it will magically work they way they want it, down to the very last
feature.

Can you find 10 installation manuals, or installation sections of a manual,
in English that discuss the actual pluses and minuses of the tool being
installed?


On Wed, Aug 27, 2014 at 4:57 PM, Óscar Fuentes <ofv@wanadoo.es> wrote:

> Jai Dayal <dayalsoap@gmail.com> writes:
>
> > No, my interpretation is correct.
> >
> > If someone writes a manual on how to fix a Ford V8 engine, the discussion
> > on the engine's fuel efficiency and safety is completely irrelevant.
> > Following your logic, one could then turn the discussion into the utility
> > of driving in general, since it may otherwise lead to more disappointed
> > people.
> >
> > His manual is about how to setup CEDET and use it. It's not about how to
> > evaluate CEDET in terms of productivity.
>
> The guide is about setting a C/C++ development environment.
>
> That means explaining how to setup tools for increasing your
> productivity. If one of the mentioned tools does not fit the bill for
> one of the use cases (C++) it is relevant to mention the fact.
>
> >>And no, it is not necessary to mention the bad ergonomics of Emacs'
> > keybindings whenever someone asks about how to configure Gnus for
> > reading e-mail.
> >
> > Why not? You just said that failing to mention the shortcomings can lead
> to
> > more disappointed people around.
>
> Exactly. If a C++ coder reads the guide and then expects from CEDET to
> provide precise smart code completion like other popular IDEs do, most
> likely he is set for a disappointment.
>
> > Following this "logic" failure to mention
> > Emacs' shortcomings during any discussion on Emacs features will lead to
> > more disappointed people around.
>
> You are a human being, not an 8-bit bot that is unable to interpret a
> message beyond simple logic rules. That's what I assume from the readers
> of help-gnu-emacs.
>
>
>