From: Yuri Khan <yuri.v.khan@gmail.com>
To: Emanuel Berg <embe8573@student.uu.se>
Cc: "help-gnu-emacs@gnu.org" <help-gnu-emacs@gnu.org>
Subject: Re: .emacs poser
Date: Wed, 18 Dec 2013 10:01:18 +0700 [thread overview]
Message-ID: <CAP_d_8VMMyXLtN_Gk9wVURfyHepqFARMVHM6mKMviyhq0uv3NA@mail.gmail.com> (raw)
In-Reply-To: <878uvjsa1k.fsf@nl106-137-194.student.uu.se>
On Tue, Dec 17, 2013 at 11:42 PM, Emanuel Berg <embe8573@student.uu.se> wrote:
>> Footnotes: [1] I have no idea why anybody would have
>> a use for that key's original function on anything
>> but a mechanic typewriter. Other than SHOUTING YOUR
>> LUNGS OUT…
>
> *And* for #define C_CONSTANT and for non-parameters in
> SQL (SELECT year ... ) - though when you think of it,
> that convention probably should be dropped. It is just
> that your eyes are used it it, so it will be like
> teaching an old dog how to sit.
Writing keywords in all caps used to be popular in case-insensitive
languages until syntax highlighting editors became the norm. Nowadays,
it’s not quite as frequent.
If/when there comes a day when most editors (IDEs?) can reliably
detect preprocessor macros and highlight them with a dangerous-looking
shade of red, the all-caps convention for #defines can also be
dropped.
next prev parent reply other threads:[~2013-12-18 3:01 UTC|newest]
Thread overview: 52+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-17 0:01 .emacs poser B. T. Raven
2013-12-17 0:36 ` Emanuel Berg
2013-12-17 1:48 ` Dale Snell
2013-12-17 2:46 ` Drew Adams
[not found] ` <mailman.9443.1387244913.10748.help-gnu-emacs@gnu.org>
2013-12-17 2:03 ` Emanuel Berg
2013-12-17 2:58 ` Dale Snell
2013-12-17 5:53 ` Jambunathan K
[not found] ` <mailman.9453.1387249112.10748.help-gnu-emacs@gnu.org>
2013-12-17 3:16 ` Emanuel Berg
2013-12-17 5:32 ` Dale Snell
2013-12-17 6:27 ` Tilman Ahr
2013-12-17 16:42 ` Emanuel Berg
2013-12-18 2:25 ` Tilman Ahr
2013-12-18 21:17 ` Emanuel Berg
2013-12-18 3:01 ` Yuri Khan [this message]
[not found] ` <mailman.9542.1387335681.10748.help-gnu-emacs@gnu.org>
2013-12-18 21:23 ` Emanuel Berg
2013-12-19 1:13 ` Yuri Khan
[not found] ` <mailman.9626.1387415627.10748.help-gnu-emacs@gnu.org>
2013-12-20 1:40 ` Emanuel Berg
[not found] ` <mailman.9460.1387258387.10748.help-gnu-emacs@gnu.org>
2013-12-17 16:17 ` Emanuel Berg
2013-12-17 17:36 ` Dale Snell
[not found] ` <mailman.9507.1387301817.10748.help-gnu-emacs@gnu.org>
2013-12-17 17:41 ` Emanuel Berg
2013-12-17 3:06 ` Yuri Khan
2013-12-17 15:17 ` Drew Adams
2013-12-18 1:38 ` Yuri Khan
2013-12-17 7:41 ` Kevin Rodgers
2013-12-17 15:24 ` Doug Lewan
[not found] ` <mailman.9465.1387266001.10748.help-gnu-emacs@gnu.org>
2013-12-17 15:40 ` Sebastien Vauban
2013-12-17 16:29 ` Drew Adams
2013-12-17 16:49 ` Emanuel Berg
2013-12-17 18:20 ` Eli Zaretskii
[not found] ` <mailman.9492.1387293902.10748.help-gnu-emacs@gnu.org>
2013-12-17 17:14 ` Emanuel Berg
2013-12-17 17:16 ` Emanuel Berg
2013-12-17 19:04 ` Doug Lewan
[not found] ` <mailman.9512.1387307070.10748.help-gnu-emacs@gnu.org>
2013-12-17 22:42 ` Emanuel Berg
2013-12-17 23:35 ` Doug Lewan
2013-12-17 21:15 ` Joost Kremers
2013-12-17 22:44 ` Emanuel Berg
2013-12-17 23:25 ` Emanuel Berg
2013-12-18 3:22 ` Jambunathan K
[not found] ` <mailman.9544.1387337046.10748.help-gnu-emacs@gnu.org>
2013-12-18 21:42 ` Emanuel Berg
[not found] ` <mailman.9628.1387418319.10748.help-gnu-emacs@gnu.org>
2013-12-19 2:52 ` Emanuel Berg
2013-12-19 3:00 ` Emanuel Berg
2013-12-20 5:31 ` Jambunathan K
2013-12-20 5:38 ` Jambunathan K
[not found] ` <mailman.9724.1387517532.10748.help-gnu-emacs@gnu.org>
2013-12-20 17:52 ` Emanuel Berg
2013-12-27 6:00 ` B. T. Raven
2013-12-27 14:12 ` Yuri Khan
2013-12-27 16:11 ` Drew Adams
[not found] ` <mailman.10526.1388160732.10748.help-gnu-emacs@gnu.org>
2013-12-29 22:17 ` B. T. Raven
2013-12-29 23:48 ` Drew Adams
2013-12-20 1:52 ` Jambunathan K
2013-12-19 22:24 ` Joost Kremers
2013-12-19 23:16 ` Emanuel Berg
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=CAP_d_8VMMyXLtN_Gk9wVURfyHepqFARMVHM6mKMviyhq0uv3NA@mail.gmail.com \
--to=yuri.v.khan@gmail.com \
--cc=embe8573@student.uu.se \
--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).