From: "Óscar Fuentes" <ofv@wanadoo.es>
To: help-gnu-emacs@gnu.org
Subject: Re: A guide on setting up C/C++ development environment for Emacs
Date: Wed, 27 Aug 2014 22:57:54 +0200 [thread overview]
Message-ID: <87ha0x8xbh.fsf@wanadoo.es> (raw)
In-Reply-To: CAMJ-YiQs5KW5=1BLxHSf_NYk6AFxMhHBH3n2VmWiodtcC62Mjg@mail.gmail.com
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.
next prev parent reply other threads:[~2014-08-27 20:57 UTC|newest]
Thread overview: 59+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-27 7:05 A guide on setting up C/C++ development environment for Emacs solidius4747
2014-08-27 12:48 ` Dmitriy Igrishin
2014-08-27 13:18 ` Tu Hoang Do
2014-08-27 14:15 ` Dmitriy Igrishin
[not found] ` <CAMd9FiKzwc1QKa3KtZPFpTGs86bupRptFqL_WwCSE3kPGARXfg@mail.gmail.com>
2014-08-27 14:53 ` Fwd: " Tu Hoang Do
[not found] ` <CAAfz9KNL25WboPXG87Azd_6yVr8zrx6hNrCsmuWs6w_XTvdspQ@mail.gmail.com>
[not found] ` <CAMd9FiJyjk78a-3yMatvca3qp+pr4O+GmDp03ZqFSkpAEoxhGw@mail.gmail.com>
2014-08-27 18:14 ` Tu Hoang Do
2014-08-27 18:15 ` Jai Dayal
2014-08-27 18:37 ` Óscar Fuentes
2014-08-27 18:42 ` Jai Dayal
2014-08-27 18:42 ` Jai Dayal
2014-08-27 18:52 ` Óscar Fuentes
2014-08-27 19:05 ` Jai Dayal
2014-08-27 19:28 ` Óscar Fuentes
2014-08-27 19:32 ` Jai Dayal
2014-08-27 20:06 ` Óscar Fuentes
2014-08-27 20:11 ` Jai Dayal
2014-08-27 20:57 ` Óscar Fuentes [this message]
2014-08-27 23:17 ` Jai Dayal
2014-08-27 23:47 ` Óscar Fuentes
[not found] ` <mailman.7678.1409181490.1147.help-gnu-emacs@gnu.org>
2014-08-28 3:30 ` Rusi
2014-08-28 3:33 ` Jai Dayal
2014-08-28 4:29 ` Óscar Fuentes
[not found] ` <mailman.7693.1409200204.1147.help-gnu-emacs@gnu.org>
2014-08-28 5:39 ` Rusi
2014-08-28 12:27 ` Jai Dayal
[not found] ` <mailman.7714.1409228889.1147.help-gnu-emacs@gnu.org>
2014-08-28 15:53 ` solidius4747
2014-08-28 21:22 ` Óscar Fuentes
2014-08-28 22:24 ` Stefan Monnier
2014-08-28 23:28 ` Dmitry
2014-08-29 0:02 ` Óscar Fuentes
[not found] ` <mailman.7793.1409270604.1147.help-gnu-emacs@gnu.org>
2014-08-29 3:35 ` Stefan Monnier
2014-08-29 6:06 ` David Engster
2014-08-29 13:09 ` Óscar Fuentes
2014-08-29 13:16 ` Jai Dayal
2014-08-29 13:45 ` Óscar Fuentes
2014-08-29 13:52 ` David Engster
2014-08-29 14:16 ` Óscar Fuentes
[not found] ` <mailman.7808.1409292429.1147.help-gnu-emacs@gnu.org>
2014-08-29 13:15 ` Rusi
2014-08-28 17:08 ` Rusi
2014-08-28 17:13 ` Jai Dayal
2014-08-28 19:43 ` Marcin Borkowski
2014-08-28 19:47 ` Jai Dayal
2014-08-28 20:15 ` Marcin Borkowski
[not found] ` <mailman.7743.1409246061.1147.help-gnu-emacs@gnu.org>
2014-08-28 17:26 ` Rusi
2014-08-28 23:01 ` Thorsten Jolitz
2014-08-27 18:45 ` Óscar Fuentes
2014-08-27 14:39 ` Thien-Thi Nguyen
[not found] ` <mailman.7608.1409150189.1147.help-gnu-emacs@gnu.org>
2014-08-27 15:01 ` solidius4747
2014-08-27 18:31 ` Óscar Fuentes
[not found] <mailman.127014.1409321829.1146.help-gnu-emacs@gnu.org>
2014-08-29 14:33 ` Tory S. Anderson
2014-08-29 17:21 ` Jai Dayal
2014-08-29 18:11 ` Marcin Borkowski
2014-08-29 18:15 ` Jai Dayal
2014-08-29 18:27 ` Marcin Borkowski
2014-08-29 18:34 ` Jai Dayal
2014-08-29 19:17 ` Marcin Borkowski
[not found] ` <mailman.7863.1409335908.1147.help-gnu-emacs@gnu.org>
2014-08-30 3:43 ` Rusi
2014-08-30 7:24 ` Thien-Thi Nguyen
2014-08-30 21:27 ` Jai Dayal
[not found] ` <mailman.7951.1409434065.1147.help-gnu-emacs@gnu.org>
2014-08-31 1:53 ` Rusi
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://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87ha0x8xbh.fsf@wanadoo.es \
--to=ofv@wanadoo.es \
--cc=help-gnu-emacs@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.
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).