unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: John Mastro <john.b.mastro@gmail.com>
To: "help-gnu-emacs@gnu.org" <help-gnu-emacs@gnu.org>
Subject: Re: use Elisp to improve your Elisp - some code issues
Date: Wed, 5 Aug 2015 17:59:29 -0700	[thread overview]
Message-ID: <CAOj2CQSaGhZ9TfwHEQmPNDeO33NgWK9ZOcvaK2tTyDjYijjxZg@mail.gmail.com> (raw)
In-Reply-To: <871tfhtibx.fsf@nl106-137-147.student.uu.se>

> If you read the code, you find the two most important
> functions are `regexp-hits-find-hit' and
> `search-regexp-in-files'. regexp means regexps!
> That there are examples - which work - applied on Lisp
> files don't change that.
>
> Now, it doesn't say *one word* about re-parsing or
> otherwise analyzing the code with respect imbecile,
> ten million times accursed computer science theory.
>
> If you want to do that - just do it! See if I will
> come and have 42 degrees of expedition fever and
> purposely misunderstand and be all negativistic.
> Of course, I will not - and why do you think that is?

Where you see negativity I think you could also see people who found
your idea interesting and are discussing ways it could be taken further.
There's no slight in that - on the contrary, I'd say it's a compliment!

-- 
john



  reply	other threads:[~2015-08-06  0:59 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <mailman.7671.1438302261.904.help-gnu-emacs@gnu.org>
2015-07-31  2:39 ` use Elisp to improve your Elisp - some code issues Pascal J. Bourguignon
2015-08-01  4:09   ` Emanuel Berg
     [not found]   ` <mailman.7712.1438402251.904.help-gnu-emacs@gnu.org>
2015-08-01  8:54     ` Pascal J. Bourguignon
2015-08-01 12:41       ` Emanuel Berg
     [not found]       ` <mailman.7727.1438432975.904.help-gnu-emacs@gnu.org>
2015-08-01 15:59         ` Pascal J. Bourguignon
2015-08-02  0:06           ` Emanuel Berg
2015-08-03  1:23             ` Ian Zimmerman
     [not found]           ` <mailman.7751.1438474104.904.help-gnu-emacs@gnu.org>
2015-08-02  0:44             ` Pascal J. Bourguignon
2015-08-02  1:29               ` Emanuel Berg
2015-08-02 15:36                 ` Robert Thorpe
2015-08-02 16:44                   ` Pascal J. Bourguignon
2015-08-05 23:40                   ` Emanuel Berg
2015-08-06  0:59                     ` John Mastro [this message]
     [not found]                 ` <mailman.7758.1438529790.904.help-gnu-emacs@gnu.org>
2015-08-02 16:25                   ` Rusi
2015-08-01 16:13       ` Michael Heerdegen
2015-07-31 20:24 ` Sam Halliday
2015-08-01  4:20   ` Emanuel Berg
2015-08-01  6:26     ` Marcin Borkowski
     [not found]     ` <mailman.7714.1438410426.904.help-gnu-emacs@gnu.org>
2015-08-01  8:57       ` Pascal J. Bourguignon
2015-08-01 12:48         ` Emanuel Berg
2015-08-01 13:05           ` Marcin Borkowski
2015-08-01 13:14             ` Emanuel Berg
2015-08-01 13:21             ` Emanuel Berg
     [not found]   ` <mailman.7713.1438402953.904.help-gnu-emacs@gnu.org>
2015-08-02 10:42     ` Sam Halliday
2015-08-05 23:21       ` Emanuel Berg
2015-07-31  0:22 Emanuel Berg
2015-07-31  2:30 ` Marcin Borkowski
2015-07-31  7:42   ` Stefan Monnier
2015-07-31 12:11   ` Navy Cheng
2015-08-03  7:56 ` Tassilo Horn

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=CAOj2CQSaGhZ9TfwHEQmPNDeO33NgWK9ZOcvaK2tTyDjYijjxZg@mail.gmail.com \
    --to=john.b.mastro@gmail.com \
    --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).