From: Artur Malabarba <bruce.connor.am@gmail.com>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: Eli Zaretskii <eliz@gnu.org>, emacs-devel <emacs-devel@gnu.org>,
Brief Busters <dgutov@yandex.ru>
Subject: Re: bug#20968: 25.0.50; Be able to specify the output directory for `byte-compile-file'
Date: Sun, 5 Jul 2015 20:30:58 +0100 [thread overview]
Message-ID: <CAAdUY-JSe+315FPMdjA5Dt7R10UbDTxvyq8bV-YjrqQKf-+mTg@mail.gmail.com> (raw)
In-Reply-To: <jwvio9yjx4x.fsf-monnier+emacsbugs@gnu.org>
2015-07-05 19:09 GMT+01:00 Stefan Monnier <monnier@iro.umontreal.ca>:
>> Then we may wish to make our answers better and more usable as well.
>
> No, we can't: we can only reply with additional info, but we can't
> retroactively fix our earlier replies. That's the difference between
> a curated answer site like SX and a mailing-list like GEH.
To be fair, that's the difference between mailing-lists and any online
forum whatsoever. Being able to edit answers is a basic requirement
for a Q&A system that wants to present quality answers that rank
highly in search engines. Being able to edit the questions themselves
is another one (since a lot of questions are asked very poorly, which
makes them difficult for other people to find).
Then there are the differences that stack-exchange presents, which are
what make them standout so much over all the other bajillion systems
that let you edit answers. Amongst them are the voting system, the
moderation philosophy, the objective-questions-only policy, and maybe
others I can't think off here.
I don't think help-gnu-emacs should strive to achieve all that. I
think it's a fine place for discussions, and an OK place for Q&A, but
trying to be awesome at Q&A (besides being a tremendous task) would
probably imply being bad at discussions (as is the case with
stack-foo).
next prev parent reply other threads:[~2015-07-05 19:30 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <23829743-922e-4304-8ab3-b762b8193860@default>
[not found] ` <74y4iytdjg.fsf@fencepost.gnu.org>
[not found] ` <e68f1dc9-9e8f-4f54-af8f-a5bb23160576@default>
[not found] ` <83pp49zb03.fsf@gnu.org>
[not found] ` <jwv8uaxp9k3.fsf-monnier+emacsbugs@gnu.org>
[not found] ` <83egkpyvvd.fsf@gnu.org>
[not found] ` <CAAdUY-+_4DzOCe6Yp19PWkxH+Ba3FGm4mCbeafho+8KodyKanQ@mail.gmail.com>
[not found] ` <83si94xrcn.fsf@gnu.org>
[not found] ` <55991ADF.8070208@yandex.ru>
[not found] ` <83pp46wu2z.fsf@gnu.org>
[not found] ` <5599450F.4050609@yandex.ru>
[not found] ` <83mvzaws3s.fsf@gnu.org>
2015-07-05 16:27 ` bug#20968: 25.0.50; Be able to specify the output directory for `byte-compile-file' Stefan Monnier
2015-07-05 16:31 ` Eli Zaretskii
2015-07-05 18:09 ` Stefan Monnier
2015-07-05 19:30 ` Artur Malabarba [this message]
2015-07-05 18:11 ` Stefan Monnier
2015-07-05 19:18 ` Artur Malabarba
2015-07-05 19:44 ` Artur Malabarba
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=CAAdUY-JSe+315FPMdjA5Dt7R10UbDTxvyq8bV-YjrqQKf-+mTg@mail.gmail.com \
--to=bruce.connor.am@gmail.com \
--cc=dgutov@yandex.ru \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=monnier@iro.umontreal.ca \
/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/emacs.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).