emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Thorsten Jolitz <tjolitz@gmail.com>
To: emacs-orgmode@gnu.org
Subject: Re: org-element-at-point fails in programming-modes
Date: Tue, 23 Sep 2014 12:29:43 +0200	[thread overview]
Message-ID: <87a95q1vfs.fsf@gmail.com> (raw)
In-Reply-To: 87ha16fcct.fsf@nicolasgoaziou.fr

Nicolas Goaziou <mail@nicolasgoaziou.fr> writes:

> Hello,
>
> Thorsten Jolitz <tjolitz@gmail.com> writes:
>
>> Ok, thanks, that sounds promising. OTOH, is the use of "\\S-" really
>> mandatory,
>
> No, it isn't.
>
>> couldn't a more robust construct be used, either something
>> like this (untested) regexp:
>>
>> ,----
>> | "[^[:space:]\\n]+"
>> `----
>
> AFAIK, [:space:] is not compatible with XEmacs. It could be "[^
> \r\t\n]+", but even this could be too broad (e.g., "#+BEGIN_..."). We
> could also limit block names to alphanumeric characters and a bunch of
> symbols.

I noticed this issue again when calling `org-element-at-point` with
point before the stars in 

,----
| ** [#A] whatsup :mytag:it:
| hello world
`----

in an emacs-lisp-mode buffer - it results in:

,----
| (paragraph (:begin 193 :end 246 :contents-begin 206 :contents-end 245
| :post-blank 1 :post-affiliated 206 ...))
`----

so it kind-of works outside org major-mode, but not correctly due to
character-class problem in the regexp(s).

PS

My org-mode is up to date

#+BEGIN_SRC emacs-lisp
 (call-interactively 'org-version)
#+END_SRC

#+results:
: Org-mode version 8.3beta (release_8.3beta-277-g698705 @
/usr/share/emacs/24.3/lisp/org/lisp/)

-- 
cheers,
Thorsten

  parent reply	other threads:[~2014-09-23 10:30 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-08-20 12:00 org-element-at-point fails in programming-modes Thorsten Jolitz
2014-08-20 12:12 ` Thorsten Jolitz
2014-08-20 12:17   ` Nick Dokos
2014-08-20 12:39     ` Sebastien Vauban
2014-08-20 14:28       ` Nick Dokos
2014-08-22  4:02         ` Nick Dokos
2014-08-22  5:22           ` Nicolas Richard
2014-08-22 13:23             ` Nick Dokos
2014-08-22 10:28           ` Thorsten Jolitz
2014-08-22 13:46             ` Nick Dokos
2014-08-22 13:53             ` Nicolas Richard
2014-08-22 14:20               ` Nicolas Richard
2014-08-22 14:26               ` Article Mode eats newlines between src-blocks (was Re: org-element-at-point fails in programming-modes) Thorsten Jolitz
2014-08-22 14:46               ` org-element-at-point fails in programming-modes Nick Dokos
2014-08-22 17:07           ` Rasmus
2014-08-20 12:41   ` Nicolas Richard
2014-08-21 20:03   ` Rasmus
2014-08-21 20:13     ` Rasmus
2014-08-21 20:35     ` Thorsten Jolitz
2014-08-21 20:49       ` Rasmus
2014-08-20 12:40 ` Nicolas Richard
2014-08-20 13:52   ` Thorsten Jolitz
2014-08-21  8:58     ` Nicolas Goaziou
2014-08-21 11:22       ` Thorsten Jolitz
2014-08-22 13:47       ` Bastien
2014-09-23 10:29       ` Thorsten Jolitz [this message]
2014-09-23 21:27         ` Nicolas Goaziou

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=87a95q1vfs.fsf@gmail.com \
    --to=tjolitz@gmail.com \
    --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
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).