all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: zokkoven@gmail.com
To: help-gnu-emacs@gnu.org
Subject: [ANN] Srefactor 0.3 with Emacs Lisp source code formatter
Date: Mon, 6 Apr 2015 11:33:52 -0700 (PDT)	[thread overview]
Message-ID: <433b00d8-a549-4b29-b21c-e6f6b1933322@googlegroups.com> (raw)

Homepage: https://github.com/tuhdo/semantic-refactor

If you are new, see the old demos for C/C++: https://github.com/tuhdo/semantic-refactor/blob/master/srefactor-demos/demos.org.

What's new in this release?

- Lot of bugs were fixed.
- Local variable renaming now has highlighting over actual variable instances to be renamed. As a reminder, actual variable instances mean that only variable instances of the same type with the same name in the same scope. For example, a user may see two variables, `A::var_1` and `B::var_1` with the same name and the same type, but only `A::var_1` is highlighted when renaming and `B::var_1` is not highlighted, because the one highlighted is in the same scope as the variable user chose to rename.
- Improve getter/setter generation:

  + Users can specify a regexp to remove a part of variable name such as prefixes like "m_" or "_".
  + Users can capitalize the first character of variable name in getter/setter with `srefactor--getter-setter-capitalize-p`. So, user can combine with `srefactor--getter-prefix ` and `srefactor--setter-prefix` to generate getters and setters like `get_Age` or `getAge` or `set_age` or `setAge`.
  + Allows getter/setter to be inserted in other file (file with the same name but different extension).

- Add initial support for Emacs Lisp refactoring with code formatting (not just indentation). See buffer formatting and one line/multiple line transformation demo: https://github.com/tuhdo/semantic-refactor/blob/master/srefactor-demos/demos-elisp.org.


                 reply	other threads:[~2015-04-06 18:33 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=433b00d8-a549-4b29-b21c-e6f6b1933322@googlegroups.com \
    --to=zokkoven@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.
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.