Nicolas Goaziou m...@nicolasgoaziou.fr writes:
Hello,
Thorsten Jolitz tjol...@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:
,
|
Hello,
Thorsten Jolitz tjol...@gmail.com writes:
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
Nick Dokos ndo...@gmail.com writes:
Nick Dokos ndo...@gmail.com writes:
Sebastien Vauban sva-n...@mygooglest.com
writes:
Nick Dokos wrote:
Thorsten Jolitz tjol...@gmail.com writes:
Thorsten Jolitz tjol...@gmail.com writes:
As a side-remark, I did send these blocks with emptly lines
Nicolas Richard theonewiththeevill...@yahoo.fr writes:
Nick Dokos ndo...@gmail.com writes:
One machine is running Gnus v. 5.13: that one smooshes the code
blocks together.
The other is running Ma Gnus v. 0.12: that one leaves empty
lines between blocks.
Do they both fontify blocks ?
Yes.
Thorsten Jolitz tjol...@gmail.com writes:
Nick Dokos ndo...@gmail.com writes:
Nick Dokos ndo...@gmail.com writes:
Sebastien Vauban sva-n...@mygooglest.com
writes:
Nick Dokos wrote:
Thorsten Jolitz tjol...@gmail.com writes:
Thorsten Jolitz tjol...@gmail.com writes:
...
Am I the only
Nicolas Goaziou m...@nicolasgoaziou.fr writes:
AFAIK, [:space:] is not compatible with XEmacs.
FWIW, I'm less and less sure why we should worry about XEmacs
compatibility. I wish some XEmacs user could step up and take
care of all these XEmacs compatibility issue.
--
Bastien
Thorsten Jolitz tjol...@gmail.com writes:
Maybe they switched to the new parser between versions, that parses a
src-block with :post-blank's, but does not take them into account when
interpreting?
I tried an experiment : (defun org-mode (rest _) t) and refresh. The
newlines didn't come back
Nicolas Richard theonewiththeevill...@yahoo.fr writes:
I would like to blame (mm-uu-dissect) but I didn't look into it.
I now blame (mm-uu-dissect). The following patch fixes it, but that part
of the code must be there for a reason... and I don't know what it is.
Modified
Nicolas Richard theonewiththeevill...@yahoo.fr writes:
Thorsten Jolitz tjol...@gmail.com writes:
Maybe they switched to the new parser between versions, that parses a
src-block with :post-blank's, but does not take them into account when
interpreting?
I tried an experiment : (defun
Nick Dokos ndo...@gmail.com writes:
Nick Dokos ndo...@gmail.com writes:
Sebastien Vauban sva-n...@mygooglest.com
writes:
Nick Dokos wrote:
Thorsten Jolitz tjol...@gmail.com writes:
Thorsten Jolitz tjol...@gmail.com writes:
As a side-remark, I did send these blocks with emptly lines
Hello,
Thorsten Jolitz tjol...@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
Nicolas Goaziou m...@nicolasgoaziou.fr writes:
Hello,
Thorsten Jolitz tjol...@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:
,
|
Hi Thorsten,
Thorsten Jolitz tjol...@gmail.com writes:
As a side-remark, I did send these blocks with emptly lines between them,
and when I look at my post in gmane the format looks alright, however
when I open it in gnus the empty lines are gone and it looks like this:
Do you by any chance
Rasmus ras...@gmx.us writes:
Thorsten Jolitz tjol...@gmail.com writes:
As a side-remark, I did send these blocks with emptly lines between them,
and when I look at my post in gmane the format looks alright, however
when I open it in gnus the empty lines are gone and it looks like this:
Do
Rasmus ras...@gmx.us writes:
Hi Rasmus,
Thorsten Jolitz tjol...@gmail.com writes:
As a side-remark, I did send these blocks with emptly lines between them,
and when I look at my post in gmane the format looks alright, however
when I open it in gnus the empty lines are gone and it looks like
Thorsten Jolitz tjol...@gmail.com writes:
Rasmus ras...@gmx.us writes:
Hi Rasmus,
Thorsten Jolitz tjol...@gmail.com writes:
As a side-remark, I did send these blocks with emptly lines between them,
and when I look at my post in gmane the format looks alright, however
when I open it in
Nick Dokos ndo...@gmail.com writes:
Sebastien Vauban sva-n...@mygooglest.com
writes:
Nick Dokos wrote:
Thorsten Jolitz tjol...@gmail.com writes:
Thorsten Jolitz tjol...@gmail.com writes:
As a side-remark, I did send these blocks with emptly lines between them,
and when I look at my post
Nick Dokos ndo...@gmail.com writes:
One machine is running Gnus v. 5.13: that one smooshes the code
blocks together.
The other is running Ma Gnus v. 0.12: that one leaves empty
lines between blocks.
Do they both fontify blocks ?
--
Nico.
Hi List,
with point at the beginning of each of the following blocks,
`org-element-at-point' does recognize the correct type when buffer is in
org-mode and other text-modes, but not so in programming modes, e.g. the
*scratch* buffer (lisp-interaction-mode). Then only the src-block is
recognized
Thorsten Jolitz tjol...@gmail.com writes:
As a side-remark, I did send these blocks with emptly lines between them,
and when I look at my post in gmane the format looks alright, however
when I open it in gnus the empty lines are gone and it looks like this:
* ORG SCRATCH
#+BEGIN_QUOTE
hallo
Thorsten Jolitz tjol...@gmail.com writes:
Thorsten Jolitz tjol...@gmail.com writes:
As a side-remark, I did send these blocks with emptly lines between them,
and when I look at my post in gmane the format looks alright, however
when I open it in gnus the empty lines are gone and it looks
Although Org functions are of course made only for working in org-mode
and its a bit hard to see at first sight how this could be useful, I
wonder if the regexps could be made a bit more general to make
`org-element-at-point' work in programming modes too (most likely this
behaviour is caused
Thorsten Jolitz tjol...@gmail.com writes:
Am I the only one seeing this? Bug in gnus/message mode?
I also see the problem. I suspect that it happens when Gnus fontifies
the blocks. Doing C-u g shows that the source of the message is
correct (i.e. has the newlines).
--
Nico.
Nick Dokos wrote:
Thorsten Jolitz tjol...@gmail.com writes:
Thorsten Jolitz tjol...@gmail.com writes:
As a side-remark, I did send these blocks with emptly lines between them,
and when I look at my post in gmane the format looks alright, however
when I open it in gnus the empty lines are
Nicolas Richard theonewiththeevill...@yahoo.fr writes:
Although Org functions are of course made only for working in org-mode
and its a bit hard to see at first sight how this could be useful, I
wonder if the regexps could be made a bit more general to make
`org-element-at-point' work in
Sebastien Vauban sva-n...@mygooglest.com
writes:
Nick Dokos wrote:
Thorsten Jolitz tjol...@gmail.com writes:
Thorsten Jolitz tjol...@gmail.com writes:
As a side-remark, I did send these blocks with emptly lines between them,
and when I look at my post in gmane the format looks alright,
26 matches
Mail list logo
