emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed

From: Rasmus <rasmus@gmx.us>
Cc: emacs-orgmode@gnu.org
Subject: Re: bug#23745: 25.0.94; Org: (pop-to-mark-command) doesn't work when using (org-open-at-point) to visit a same-file link
Date: Sat, 11 Jun 2016 13:37:37 +0200	[thread overview]
Message-ID: <8760tgx8fy.fsf@gmx.us> (raw)
In-Reply-To: <87twh01tfu.fsf@secretsauce.net> (Dima Kogan's message of "Fri, 10 Jun 2016 17:05:09 -0700")

The following message is a courtesy copy of an article
that has been posted to gmane.emacs.bugs as well.

Hi Dima,

Thanks for the report.

Dima Kogan <dima@secretsauce.net> writes:

> =====================
> * aaaa
> bbbbb
>
> * cccc
> [[aaaa]]
> =====================
>
> With the point at the [[aaaa]] link, I can visit the aaaa heading with
> C-c C-o (org-open-at-point), and I can go back to where I was with the
> org-specific C-c & (org-mark-ring-goto). But I should also be able to go
> back with C-u C-SPC (effectively pop-to-mark-command), since that works
> for inside-the-same-buffer jumps in all other emacs context, including
> non-org ones. I suspect all we would need to do is to
> (push-mark-command) before we jump in (org-open-at-point). Is this
> simply forgotten, or was it omitted on purpose? If the former, I'll post
> a patch.

I think you are right; your description of behavior would be consistent.
Note that once I click C-c & at "* aaaa" and thus return to the link
"[[aaaa]]" I can pop the mark to go back to "* aaaa" but the reverse is
not possible.

A fix for this would be appreciated.

Thanks,
Rasmus

-- 
Send from my Emacs

next      parent reply	other threads:[~2016-06-11 11:37 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <87twh01tfu.fsf@secretsauce.net>
2016-06-11 11:37 ` Rasmus [this message]
2018-02-27  0:10 ` bug#23745: 25.0.94; Org: (pop-to-mark-command) doesn't work when using (org-open-at-point) to visit a same-file link Nicolas Goaziou
2018-02-27  2:12   ` bug#23745: " Samuel Wales
2018-02-27  2:12   ` Samuel Wales

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=8760tgx8fy.fsf@gmx.us \
    --to=rasmus@gmx.us \
    --cc=emacs-orgmode@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

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).