all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Francis Belliveau <f.belliveau@comcast.net>
To: "B.V. Raghav" <bvraghav@iitk.ac.in>
Cc: help-gnu-emacs@gnu.org
Subject: Re: Compilation in C and ADA
Date: Sat, 23 Jul 2016 10:22:22 -0400	[thread overview]
Message-ID: <1D8794DF-16FD-43C6-8F74-43EAFC1B6D0A@comcast.net> (raw)
In-Reply-To: <87y44xors9.fsf@ram.bvr.dp.lan>

I guess I need to clarify what I meant about "Human Factors Ambiguity" a bit.

If a menu selection says "compile" then "compile" is what it should be trying to do, not "make".  This is simply a matter if naming things so that they set expectations properly and eliminate the need to read documentation up front.

Put aside the ability to customize things.  That is necessary due to the diversity of development environments, etc.

If I see a command like "compile" in a menu, I expect it to call the compiler for me, not attempt to "make" my project.

Fran


  reply	other threads:[~2016-07-23 14:22 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-07-19 11:11 Compilation in C and ADA Edward Zacharek
2016-07-19 17:36 ` B.V. Raghav
2016-07-20  2:50   ` Francis Belliveau
2016-07-20  4:30     ` B.V. Raghav
2016-07-23 14:22       ` Francis Belliveau [this message]
2016-07-23 17:52         ` Dale Snell
     [not found]         ` <mailman.1937.1469296394.26859.help-gnu-emacs@gnu.org>
2016-07-23 20:08           ` Emanuel Berg
     [not found]       ` <mailman.1922.1469283823.26859.help-gnu-emacs@gnu.org>
2016-07-23 15:05         ` Emanuel Berg
2016-07-24  4:20           ` Francis Belliveau
     [not found]           ` <mailman.1955.1469334108.26859.help-gnu-emacs@gnu.org>
2016-07-24 12:48             ` Emanuel Berg
2016-07-23 16:23 ` Kendall Shaw
     [not found] <mailman.1680.1468936015.26859.help-gnu-emacs@gnu.org>
2016-07-20  3:43 ` 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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1D8794DF-16FD-43C6-8F74-43EAFC1B6D0A@comcast.net \
    --to=f.belliveau@comcast.net \
    --cc=bvraghav@iitk.ac.in \
    --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.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.