From: Nick Dokos <firstname.lastname@example.org>
To: Dan Davison <email@example.com>
Cc: emacs org-mode mailing list <firstname.lastname@example.org>
Subject: Re: overzealous file link creation
Date: Tue, 11 Aug 2009 17:36:28 -0400 [thread overview]
Message-ID: <email@example.com> (raw)
In-Reply-To: Message from Dan Davison <firstname.lastname@example.org> of "Tue, 11 Aug 2009 16:29:56 EDT." <email@example.com>
Dan Davison <firstname.lastname@example.org> 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
> 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.
> def f(filepath):
> *def g(arg):
> return arg
> This is with latest git.
I cannot reproduce this. I created foo.py with the above contents, deleted
the asterisks, saved the file and then tried M-x org-cycle at the various
places indicated by the asterisks. In no case does a "file" disappear.
At the three places around filepath in function f(), nothing happens.
At the beginning of the def g(...), it folds the function (I also tried
at the beginning of the definition of f, with the same result). In all of
these cases, the buffer does not get modified.
The only case where the buffer is modified is at the beginning of the empty
line between the functions: I get a tab added (actually a bunch of spaces -
not sure whether it makes a difference but I set indent-tabs-mode to nil).
I think we need more people to try out the experiment!-)
next prev parent reply other threads:[~2009-08-11 21:38 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 [this message]
2009-08-12 7:52 ` Manish
2009-08-12 8:32 ` Carsten Dominik
2009-08-12 8:30 ` Carsten Dominik
2009-08-12 16:09 ` Dan Davison
2009-08-12 16:42 ` Carsten Dominik
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 \
* 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).