unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Emanuel Berg <embe8573@student.uu.se>
To: help-gnu-emacs@gnu.org
Subject: Re: Fire defun by typing keyword
Date: Tue, 05 Nov 2013 23:38:14 +0100	[thread overview]
Message-ID: <87k3gmbhjk.fsf@nl106-137-194.student.uu.se> (raw)
In-Reply-To: mailman.5372.1383685981.10748.help-gnu-emacs@gnu.org

Kai Großjohann <kai.grossjohann@gmx.net> writes:

> for (int i=0; i<10; i++) {
>     _
> }
>
> You could create an abbrev that reads a type (int), a
> variable (i), an initial value (0), a final value
> (10), and then produces the above, where _ indicates
> the position of the cursor.

Wow! I actually had that exact same thought a couple of
years ago:

http://unix.stackexchange.com/questions/71599

Back then I thought there was basically no thinking at
all to programming, it was just a matter of finger
habits, eye-hand coordination, eye-brain interpretation
(as opposed to the crude "reading"), etc., all physical
in one way or another. Typing and everything should be
so fast so it could "keep up" with the thinking (which
was trivial in a pleasant, not boring, sense).

While I still think this aspect is grossly overlooked, I
don't think it is "all about that" anymore. I certainly
have the time to write a for loop now and then without
my mind beaming away in some other direction, hopelessly
lost forever after.

But it is an amazing thought - imagine to have an entire
programming language coded anew like that, with every
construct just a short abbrev away. It would make for
"parametric" programming if there ever was one.

-- 
Emanuel Berg, programmer-for-rent. CV, projects, etc at uXu
underground experts united:  http://user.it.uu.se/~embe8573


  parent reply	other threads:[~2013-11-05 22:38 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-10-30  2:38 Fire defun by typing keyword Emanuel Berg
2013-10-30  3:05 ` Stefan Monnier
2013-10-30  3:23 ` Kevin Rodgers
     [not found] ` <mailman.4950.1383102623.10748.help-gnu-emacs@gnu.org>
2013-11-01 18:58   ` Emanuel Berg
2013-11-05  2:50   ` Emanuel Berg
2013-11-05 21:12     ` Kai Großjohann
     [not found]     ` <mailman.5372.1383685981.10748.help-gnu-emacs@gnu.org>
2013-11-05 22:38       ` Emanuel Berg [this message]
2013-11-06  3:37         ` Rustom Mody
2013-11-06 22:32           ` Emanuel Berg
2013-11-07  1:16             ` Rustom Mody
2013-11-07 12:07               ` Alan Schmitt
2013-11-07 14:31                 ` Peter Dyballa
2013-11-07 14:47                 ` Rustom Mody
2013-11-07 16:21                   ` Peter Dyballa
     [not found]                   ` <mailman.5498.1383841291.10748.help-gnu-emacs@gnu.org>
2013-11-07 16:31                     ` Rustom Mody
2013-11-07 19:49                       ` Emanuel Berg
2013-11-08  2:27                         ` Rustom Mody
2013-11-08  9:45                           ` Peter Dyballa
2013-11-09  1:14                           ` Emanuel Berg
2013-11-09 21:24                             ` John Bokma
2013-11-09 21:59                               ` Emanuel Berg
2013-11-09 22:14                               ` Emanuel Berg
2013-11-11 17:50                           ` Emanuel Berg
2013-11-08 12:14                   ` Alan Schmitt
     [not found]                 ` <mailman.5488.1383834710.10748.help-gnu-emacs@gnu.org>
2013-11-08 12:13                   ` Alan Schmitt
2013-11-08 12:30                     ` Peter Dyballa
2013-11-09 22:26         ` Kai Großjohann
     [not found]         ` <mailman.5668.1384036032.10748.help-gnu-emacs@gnu.org>
2013-11-09 23:45           ` 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=87k3gmbhjk.fsf@nl106-137-194.student.uu.se \
    --to=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).