unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Richard Kim <Richard.Kim1@synopsys.com>
To: 5666@debbugs.gnu.org
Subject: bug#5666: 23.1; please define push-tag-mark in etags.el
Date: Mon, 01 Mar 2010 11:27:05 -0800	[thread overview]
Message-ID: <qtm635fu9km.fsf@rutro-cane1.internal.synopsys.com> (raw)

GNU/Emacs defines pop-tag-mark command to go along with find-tag
command for traversing back in cursor movement history.  However
GNU/Emacs does not define matching push-tag-mark command.  I would
like to request that something like the following be added to etags.el

  (defun push-tag-mark ()
    "Push the current position to the ring of markers so that
    \\[pop-tag-mark] can be used to come back to current position."
    (interactive)
    (ring-insert find-tag-marker-ring (point-marker)))

I make this request for the following reasons:

- This is a useful command by itself which I use often

- This would be useful for use by tools other than etags, e.g.,
  forthcoming cedet tool or even for existing tools, e.g.,

    (defadvice imenu
      (before use-etags-stack activate compile)
      "Push point onto stack used by etags so that \\[pop-tag-mark] can be used."
      (push-tag-mark))

    (defadvice cscope-call
      (before use-etags-stack activate compile)
      "Push point onto stack used by etags so that \\[pop-tag-mark] can be used."
      (push-tag-mark))

- Since xemacs defines push-tag-mark already, it makes it easier for
  tool developers, so that we don't have to add code such as the
  following in our own packages:

  (unless (fboundp 'push-tag-mark)
    (defun push-tag-mark ()
      (interactive)
      (ring-insert find-tag-marker-ring (point-marker))))

Thanks.







             reply	other threads:[~2010-03-01 19:27 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-01 19:27 Richard Kim [this message]
2019-10-01 15:41 ` bug#5666: 23.1; please define push-tag-mark in etags.el Lars Ingebrigtsen

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=qtm635fu9km.fsf@rutro-cane1.internal.synopsys.com \
    --to=richard.kim1@synopsys.com \
    --cc=5666@debbugs.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 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).