unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Luke Lee <luke.yx.lee@gmail.com>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: emacs-devel@gnu.org
Subject: Re: Fwd: Update earlier posted hideif.el enhancements
Date: Wed, 4 Dec 2013 10:06:42 +0800	[thread overview]
Message-ID: <CAA=xLRPbXB8=Eqm0NmVPv4V_GZ=5AxJDMe_-wa=XYhW-FiYixA@mail.gmail.com> (raw)
In-Reply-To: <jwv38maxdqb.fsf-monnier+emacs@gnu.org>

[-- Attachment #1: Type: text/plain, Size: 1560 bytes --]

>I guess we should use the CEDET infrastructure for that (which would
>also make it possible to scan files which aren't currently visited).

Indeed, I tried CEDET for several years but it always have problems here
or there. After I patch this, that failed.. My embedded system C++ code
contains some non-standard extensions that always causing CEDET
fail so I decide to go hideif solution since it's much smaller :-) and does
not that much rely on the previous parsing contexts to continue parsing.

>But I guess for now we can try your "quick&dirty" solution of making the
>settings global.

I got no better idea but providing one more custom option for that.
Personally I always open different Emacs for different projects with
each its own local session/desktop/... settings; while leaving emacs
server for other general purpose use.

>This does not use the commit history.  Instead it kind of "creates
>a brand new and clean history".

I see. After some thoughts it's still worthwhile even if I do the
cherry-picking
since I've been troubled by those kind of complicate nested #if..#endif
for years and I believe a lot others should have similar problems too.

By the way, what "certification" (sorry that I can't think of a better
word)
is required to be able to commit code directly into the main Emacs
repository (or a branch)? I'm currently working on auto *.h scanning
for hideif.el in my spare time. Maybe there will be more updates some
weeks/months later.

I'll send out two or three patches when I completed the splitting.

Best regards,
Luke Lee

[-- Attachment #2: Type: text/html, Size: 5967 bytes --]

  reply	other threads:[~2013-12-04  2:06 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-08  1:59 Update earlier posted hideif.el enhancements Luke Lee
2013-11-08  2:54 ` Stefan Monnier
2013-11-08  4:07   ` Luke Lee
2013-11-24 17:50     ` Stefan Monnier
     [not found]       ` <CAA=xLROospEnRM_Es0bBkQUpC_RmrS-vQDxprD2it+fVDbVKog@mail.gmail.com>
2013-11-25  6:35         ` Fwd: " Luke Lee
2013-11-29 21:59           ` Stefan Monnier
2013-12-03  4:33             ` Luke Lee
2013-12-03 13:45               ` Stefan Monnier
2013-12-04  2:06                 ` Luke Lee [this message]
2013-12-04 15:28                   ` Luke Lee
2013-12-04 17:33                     ` Stefan Monnier

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='CAA=xLRPbXB8=Eqm0NmVPv4V_GZ=5AxJDMe_-wa=XYhW-FiYixA@mail.gmail.com' \
    --to=luke.yx.lee@gmail.com \
    --cc=emacs-devel@gnu.org \
    --cc=monnier@iro.umontreal.ca \
    /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 public inbox

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

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).