emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Bastien <bzg@gnu.org>
To: Ian Kelling <ian@iankelling.org>
Cc: Sebastien Vauban
	<public-sva-news-D0wtAvR13HarG/iDocfnWg@plane.gmane.org>,
	emacs-orgmode@gnu.org
Subject: Re: [PATCH] Make the point visible when jumping to the mark
Date: Fri, 23 May 2014 07:47:25 +0200	[thread overview]
Message-ID: <87wqddf3ma.fsf@bzg.ath.cx> (raw)
In-Reply-To: <87y4xt4yaw.fsf@treetowl.lan> (Ian Kelling's message of "Thu, 22 May 2014 08:40:07 -0700")

Hi Ian,

Ian Kelling <ian@iankelling.org> writes:

> I would be happy to write the patch for this, if we agree.

Anything that gets rid of advice is good, we agree on this.

If you have time, please start sketching out the patch so that we can
discuss how to replace some of the advice by internal Org functions.
Note that we will certainly hit some roadblocks, and we don't want to
replace core Emacs fonctions like `pop-to-mark'.

One possible outcome is to consider a new Emacs hook: something like
`after-interactive-point-move-hook' that would check if the current
buffer is in Org and would reveal the context systematically.

I haven't thought this through, but raising this needs on the
emacs-devel list will perhaps leads to something.

Otherwise, having a contributed package with advice (using
add-function instead of defadvice) would be good enough.

Thanks!

-- 
 Bastien

  reply	other threads:[~2014-05-23  5:47 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-01  4:54 [PATCH] Make the point visible when jumping to the mark Ian Kelling
2014-05-20 22:25 ` Ian Kelling
2014-05-21  2:58   ` Bastien
2014-05-21  9:21     ` Ian Kelling
2014-05-21 13:00 ` Bastien
2014-05-21 19:01   ` Ian Kelling
2014-05-22  9:54     ` Bastien
2014-05-22  8:56   ` Sebastien Vauban
2014-05-22  9:52     ` Bastien
2014-05-22 15:40       ` Ian Kelling
2014-05-23  5:47         ` Bastien [this message]
  -- strict thread matches above, loose matches on Subject: below --
2013-09-15  9:22 Ian Kelling
2013-09-15 17:25 ` Ian Kelling

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.orgmode.org/

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

  git send-email \
    --in-reply-to=87wqddf3ma.fsf@bzg.ath.cx \
    --to=bzg@gnu.org \
    --cc=emacs-orgmode@gnu.org \
    --cc=ian@iankelling.org \
    --cc=public-sva-news-D0wtAvR13HarG/iDocfnWg@plane.gmane.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/org-mode.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).