all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Iustin Pop <iustin@google.com>
To: emacs-devel@gnu.org
Subject: [PATCH] etags: Add a small list of interpretors for Python
Date: Thu, 19 Aug 2010 17:36:06 +0200	[thread overview]
Message-ID: <20100819153606.GO4157@google.com> (raw)

Currently, etags has no interpretors defined for Python, which prevents
it from recognising Python scripts that have no extension. This patch
adds a small list of interpretors for this language, which while not
perfect (e.g. it will fail on specific versions like python2.4), it is
better than the current situation where all scripts without an extension
will default to Fortran.

Note: I debated adding a more detailed list, but it would get outdated
quickly, so I left just these three versions. A regular expression for
the interpreter name would be much better here, would implementing that
make sense?

[please keep me CC-ed, I'm not subscribed to the list]

=== modified file 'lib-src/etags.c'
*** lib-src/etags.c	2010-08-11 08:20:34 +0000
--- lib-src/etags.c	2010-08-19 13:27:43 +0000
*************** line.";
*** 755,760 ****
--- 755,762 ----
  
  static const char *Python_suffixes [] =
    { "py", NULL };
+ static const char *Python_interpreters [] =
+   { "python", "python2", "python3", NULL };
  static const char Python_help [] =
  "In Python code, `def' or `class' at the beginning of a line\n\
  generate a tag.";
*************** static language lang_names [] =
*** 836,842 ****
    { "postscript",PS_help,        PS_functions,      PS_suffixes        },
    { "proc",      no_lang_help,   plain_C_entries,   plain_C_suffixes   },
    { "prolog",    Prolog_help,    Prolog_functions,  Prolog_suffixes    },
!   { "python",    Python_help,    Python_functions,  Python_suffixes    },
    { "scheme",    Scheme_help,    Scheme_functions,  Scheme_suffixes    },
    { "tex",       TeX_help,       TeX_commands,      TeX_suffixes       },
    { "texinfo",   Texinfo_help,   Texinfo_nodes,     Texinfo_suffixes   },
--- 838,844 ----
    { "postscript",PS_help,        PS_functions,      PS_suffixes        },
    { "proc",      no_lang_help,   plain_C_entries,   plain_C_suffixes   },
    { "prolog",    Prolog_help,    Prolog_functions,  Prolog_suffixes    },
!   { "python",Python_help,Python_functions,Python_suffixes,NULL,Python_interpreters},
    { "scheme",    Scheme_help,    Scheme_functions,  Scheme_suffixes    },
    { "tex",       TeX_help,       TeX_commands,      TeX_suffixes       },
    { "texinfo",   Texinfo_help,   Texinfo_nodes,     Texinfo_suffixes   },




             reply	other threads:[~2010-08-19 15:36 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-08-19 15:36 Iustin Pop [this message]
2010-09-01 11:53 ` [PATCH] etags: Add a small list of interpretors for Python Iustin Pop
2010-09-01 13:09 ` Francesco Potortì
2010-12-23 14:13   ` Iustin Pop
2011-01-12 16:43     ` Francesco Potortì

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20100819153606.GO4157@google.com \
    --to=iustin@google.com \
    --cc=emacs-devel@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.
Code repositories for project(s) associated with this external index

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

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.