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

[Óscar Fuentes]

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.