From: Stefan Huchler <stefan.huchler@mail.de>
To: help-gnu-emacs@gnu.org
Subject: Re: strange behaviour in keyboard macro
Date: Wed, 09 Aug 2017 08:18:35 +0200 [thread overview]
Message-ID: <87valx2ric.fsf@mail.de> (raw)
In-Reply-To: 86shhdynd2.fsf@zoho.com
Emanuel Berg <moasen@zoho.com> writes:
> Will be inferior, always. And they don't lead
> anywhere. Elisp on the contrary leads to more
> Elisp, to the destruction of many young men's
> careers and so on. But what do you need
> a career for when you have Elisp?
>
> TEHO, of course.
Ahh lol, so I am not the only one :D with no career :)
Well had none before I learned elisp, but I feel like elisp makes shure
that I never will have one :D
next prev parent reply other threads:[~2017-08-09 6:18 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-30 5:51 strange behaviour in keyboard macro Héctor Lahoz
2017-07-30 7:26 ` Emanuel Berg
2017-07-30 10:01 ` Héctor Lahoz
2017-07-30 13:46 ` Emanuel Berg
2017-07-30 20:19 ` Marcin Borkowski
2017-07-30 21:47 ` Emanuel Berg
2017-07-31 4:40 ` Marcin Borkowski
2017-07-31 9:19 ` Emanuel Berg
2017-08-09 6:18 ` Stefan Huchler [this message]
2017-07-30 13:50 ` 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=87valx2ric.fsf@mail.de \
--to=stefan.huchler@mail.de \
--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).