all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Gary <help-gnu-emacs@garydjones.name>
To: help-gnu-emacs@gnu.org
Subject: Re: Automatically commenting changes
Date: Tue, 25 Jan 2011 11:48:05 +0100	[thread overview]
Message-ID: <ihm9p5$97h$1@dough.gmane.org> (raw)
In-Reply-To: AANLkTikKvgCe2_6_4ypfASS0rf-sqTjTgfkJ3rH7Sigf@mail.gmail.com

Deniz Dogan wrote:
> 2011/1/25 Gary :
>> An editor I used long long ago had the ability to tag lines you
> changed
>> with your name (or some other customisable character sequence).
..
>> Does anything like this exist for emacs?

> Are you sure you want the code riddled with comments all over the
> place?

For three-way merges it was invaluable - if all my changes are tagged,
then it is much easier to see exactly what I have changed. Similarly
during the actual coding, I could find changes very quickly. Commit
those "tags", obviously, would be absurd - actually, I'm not convinced
that whatever editor it was didn't simply display them in the buffer,
but maintained them in a different file or files (I am talking about
something I used about 20 years ago, so can't remember the details).




  reply	other threads:[~2011-01-25 10:48 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-01-25  9:40 Automatically commenting changes Gary
2011-01-25  9:46 ` Deniz Dogan
2011-01-25 10:48   ` Gary [this message]
2011-01-25 18:38     ` Thierry Volpiatto
     [not found] <mailman.1.1295948439.29299.help-gnu-emacs@gnu.org>
2011-01-25 10:09 ` Pascal J. Bourguignon
2011-01-26  3:32 ` Stefan Monnier
2011-01-26 13:21   ` Gary
     [not found]   ` <mailman.0.1296048116.12534.help-gnu-emacs@gnu.org>
2011-01-26 13:57     ` Richard Riley
2011-01-26 16:05       ` Gary
     [not found]       ` <mailman.2.1296057926.30134.help-gnu-emacs@gnu.org>
2011-01-26 19:54         ` Tim X
2011-01-27  2:16         ` Stefan Monnier
2011-01-26 15:55     ` 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

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

  git send-email \
    --in-reply-to='ihm9p5$97h$1@dough.gmane.org' \
    --to=help-gnu-emacs@garydjones.name \
    --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.