From: Oleksandr Gavenko <gavenkoa@gmail.com>
To: help-gnu-emacs@gnu.org
Subject: Re: (require ...) and file dependencies.
Date: Sat, 03 Jan 2015 16:51:06 +0200 [thread overview]
Message-ID: <87oaqfapet.fsf@gavenkoa.example.com> (raw)
In-Reply-To: 87tx08obja.fsf@debian.uxu
On 2015-01-03, Emanuel Berg wrote:
> Dmitry Gutov <dgutov@yandex.ru> writes:
>
>>> Seems that proper way to fix issue is by
>>> rearranging dependency hierarchy by breaking
>>> dependency cycles, isn't?
>>
>> That would be even better, of course.
>
> And more pleasant and rewarding to do, as well. Just
> go with the flow, man :)
I fix compilation warnings and errors in wesnoth-mode.
It have wesnoth-mode.el and wesnoth-update.el (for generating validation
schema and context sensitive completion). wesnoth-update.el uses some core
parsing function from wesnoth-mode.el and author define key binding to
wesnoth-update.el from wesnoth-mode.el...
To fix issues large parts of code must migrate between files and DVCS
blame/annotate history was lost in refactoring.
That limitation I hate in VCS. So you have to store detailed copy/paste info
in commit message or intensively grep and "DVCS update -r rev" to figure out
original place of defun to get know who/when and what fixes done with that
defun.
--
Best regards!
next prev parent reply other threads:[~2015-01-03 14:51 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-27 23:42 (require ...) and file dependencies Oleksandr Gavenko
2014-12-27 23:59 ` Oleksandr Gavenko
2014-12-28 0:09 ` Dmitry Gutov
[not found] ` <mailman.16797.1419724814.1147.help-gnu-emacs@gnu.org>
2014-12-28 0:24 ` Stefan Monnier
[not found] ` <mailman.16798.1419725386.1147.help-gnu-emacs@gnu.org>
2015-01-03 2:14 ` Emanuel Berg
2015-01-03 14:51 ` Oleksandr Gavenko [this message]
[not found] ` <mailman.17173.1420296692.1147.help-gnu-emacs@gnu.org>
2015-01-03 17:34 ` Emanuel Berg
[not found] <mailman.16796.1419723800.1147.help-gnu-emacs@gnu.org>
2014-12-28 0:22 ` Stefan Monnier
2015-01-03 14:04 ` Oleksandr Gavenko
2015-01-03 14:30 ` Oleksandr Gavenko
2015-01-03 2:12 ` Emanuel Berg
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=87oaqfapet.fsf@gavenkoa.example.com \
--to=gavenkoa@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).