From: John Yates <john@yates-sheets.org>
To: Dmitry Gutov <dgutov@yandex.ru>
Cc: "Óscar Fuentes" <ofv@wanadoo.es>,
"Emacs developers" <emacs-devel@gnu.org>
Subject: Re: Rename refactoring, or something like that
Date: Tue, 17 Nov 2015 06:10:46 -0500 [thread overview]
Message-ID: <CAJnXXogekhuod-0R93X6LohRuSY6fQTZK_YZJjg44SamcBrPwA@mail.gmail.com> (raw)
In-Reply-To: <564A424A.2070904@yandex.ru>
[-- Attachment #1: Type: text/plain, Size: 668 bytes --]
As part of an improved UI I would hope that if I rename an identifier to an
identifier of a different length there will be an easy way to visit the
sites of the renames to fix up formatting (primarily adjusting whitespace
and/or lines that have become too long).
If the rename is not based on a strong semantic framework (e.g. in the C++
world something that can truly grok all of the name resolution rules) then
there will need to be some means of incorporating human input (a la
query-and-replace). If such querying occurs on a site by site basis then
there could be a query respone that says "yes, do the rename but then pause
and let me do some editing".
/john
[-- Attachment #2: Type: text/html, Size: 996 bytes --]
next prev parent reply other threads:[~2015-11-17 11:10 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-15 4:43 Rename refactoring, or something like that Dmitry Gutov
2015-11-16 10:03 ` joakim
2015-11-16 10:17 ` Dmitry Gutov
2015-11-16 11:47 ` A better UI than perform-replace (was: Rename refactoring, or something like that) Oleh Krehel
2015-11-16 18:01 ` A better UI than perform-replace Dmitry Gutov
2015-11-16 22:37 ` A better UI than perform-replace (was: Rename refactoring, or something like that) Drew Adams
2015-11-17 23:52 ` A better UI than perform-replace John Wiegley
2015-11-17 22:57 ` A better UI than perform-replace (was: Rename refactoring, or something like that) Richard Stallman
2015-11-18 0:55 ` A better UI than perform-replace Juri Linkov
2015-11-18 1:40 ` Drew Adams
2015-11-18 12:32 ` Dmitry Gutov
2015-11-19 0:57 ` Juri Linkov
2015-11-19 1:16 ` Dmitry Gutov
2015-11-20 0:40 ` Juri Linkov
2015-11-21 18:23 ` Dmitry Gutov
2015-11-19 12:46 ` John Yates
2015-11-19 16:31 ` John Wiegley
2015-11-19 19:11 ` John Yates
2015-11-19 19:18 ` John Wiegley
2015-11-20 8:06 ` Adrian.B.Robert
2015-11-19 19:46 ` David Kastrup
2015-11-19 22:03 ` Drew Adams
2015-11-20 0:42 ` Juri Linkov
2015-11-20 8:12 ` Eli Zaretskii
2015-11-18 8:50 ` Andreas Schwab
2015-11-21 1:41 ` Eric Ludlam
2015-11-16 13:13 ` Rename refactoring, or something like that Óscar Fuentes
2015-11-16 20:53 ` Dmitry Gutov
2015-11-17 11:10 ` John Yates [this message]
2015-11-17 13:14 ` Dmitry Gutov
2015-11-17 15:57 ` John Yates
2015-11-16 16:01 ` Eli Zaretskii
2015-11-16 16:03 ` Dmitry Gutov
2015-11-16 17:18 ` Eli Zaretskii
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=CAJnXXogekhuod-0R93X6LohRuSY6fQTZK_YZJjg44SamcBrPwA@mail.gmail.com \
--to=john@yates-sheets.org \
--cc=dgutov@yandex.ru \
--cc=emacs-devel@gnu.org \
--cc=ofv@wanadoo.es \
/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).