emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Carsten Dominik <carsten.dominik@gmail.com>
To: Dan Davison <davison@stats.ox.ac.uk>
Cc: emacs org-mode mailing list <emacs-orgmode@gnu.org>
Subject: Re: overzealous file link creation
Date: Wed, 12 Aug 2009 10:30:12 +0200	[thread overview]
Message-ID: <B9802B4B-62A6-47E3-AA3A-4362F7C1C39A@gmail.com> (raw)
In-Reply-To: <87ws5aozzv.fsf@stats.ox.ac.uk>

On Aug 11, 2009, at 10:29 PM, Dan Davison wrote:

> Recently I've been randomly losing the string 'file' from all sorts of
> documents. Up until now I had no explanation. It's not the sort of
> question one wants to ask on public mailing lists.
> OK, so if you call org-cycle "in the vicinity" of a word that starts
> with the string 'file', then it eats up 'file' and prompts for link
> insertion. This is true in buffers that are not in org-mode or
> orgstruct*-mode. (I call org-cycle the whole time in order to use
> outline-minor-mode, but o-m-m doesn't have to be turned on to cause
> this.)
> Try putting the following fragment into python-mode, and getting rid  
> of
> the asterisks. Then org-cycle issued with point at any of the  
> asterisked
> locations eats the string 'file' and prompts for a link.
> --8<---------------cut here---------------start------------->8---
> def f(filepath):
>    print(
>        *filepath*)*
> *
> *def g(arg):
>    return arg
> --8<---------------cut here---------------end--------------->8---
> This is with latest git.

Hi Dan,

could you please check the following variables:


Probably one of these contains a function that will do file link  

- Carsten

  parent reply	other threads:[~2009-08-12  8:30 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-08-11 20:29 overzealous file link creation Dan Davison
2009-08-11 21:36 ` Nick Dokos
2009-08-12  7:52 ` Manish
2009-08-12  8:32   ` Carsten Dominik
2009-08-12  8:30 ` Carsten Dominik [this message]
2009-08-12 16:09   ` Dan Davison
2009-08-12 16:42     ` Carsten Dominik

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:

  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=B9802B4B-62A6-47E3-AA3A-4362F7C1C39A@gmail.com \
    --to=carsten.dominik@gmail.com \
    --cc=davison@stats.ox.ac.uk \
    --cc=emacs-orgmode@gnu.org \


* 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


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