Hi Volker
On Fri, Mar 21, 2014 at 1:31 AM, Volker Strobel
wrote:
> My problem is, that this remote reference starts in row 3 (because of @$#),
> however, I'd like to start in row 2 (that means @$#-1). However, this
> relative reference does not seem to work here.
Calculation within the field ref
Hello Yasuhito,
Yasuhito Takamiya writes:
> Hello all,
>
> For your information, to anyone interested in GTD and org-mode,
> I am developing a tiny tool for org-mode to schedule your agenda tasks
> easily like Mailbox iPhone app (http://www.mailboxapp.com/).
>
> https://github.com/yasuhito/orgbo
ATTN: Users of ODT exporter
If you want to talk to me wrt exporter, please add a note here:
http://www.emacswiki.org/emacs/Jambunathan_K
I am leaving this list.
I WILL NEVER MAKE an assignment to Emacs. i.e. The development that
happens on my repository will NEVER hit the Emacs trunk.
Hi Glenn,
Glenn Morris writes:
> Package: emacs,org-mode
> Version: 24.3.50
>
> This refers to the version of Org mode in Emacs trunk.
>
> ./src/emacs -Q -l ox-odt
> C-h v org-odt-data-dir
> -> Its value is "/usr/share/emacs/etc/org"
>
> This value is hard-coded (and autoloaded; why?) in org-v
Hi Sébastien,
"Sebastien Vauban"
writes:
> Though the "deadline-up" sorting does not work, as demo'ed in the
> previous post.
Can you point at that post again?
Also, the example in your previous email is quite complex.
If something does not work in `org-agenda-sorting-strategy'
can you make
* Nicolas Goaziou wrote:
> Hello,
Hi Nicolas!
> Karl Voit writes:
>
>> Currently, I do have some issues like [1] which sometimes cause "loss
>> of data" [2] and multiple times a day(!) my Emacs enters some endless
>> loop so that I have to kill it [3]. Very annoying and frustrating.
>>
>> There
Hi Samuel,
Samuel Wales writes:
> "[bug] [babel] babel corrupts undo history"
I've reread this thread but I currently nothing wrong with
undoing wrt source code editing.
Let me know if I missed something, thanks,
--
Bastien
Hi Joe,
Joe Hirn writes:
> Against the latest master:
can you repost the patch by creating another thread with [PATCH]
in the subject line, and using plain text instead of HTML format?
If you don't use plain text email, simply attach the patch instead
of including it in the body of the email.
Hi Charles,
Charles Millar writes:
> I guess it's fixed.
Thanks for confirming,
--
Bastien
Charles Berry writes:
> Andreas Leha med.uni-goettingen.de> writes:
>
>>
>> Hi Michael,
>>
>> Michael Weylandt gmail.com> writes:
>>
>> > Hi,
>> >
>> > I want to put a summary of my analysis at the beginning of a document
>> > using results calculated at the end of the document. Is this pos
Hi,
"G. Martin Butz" writes:
> While importing and viewing one of my org files, I do get strange results:
>
> + I only see dates from DONE-entries
> + There might be e.g. an entry in the ical file/Iceowl dated to
> 09:57, 2nd of December 2013
> + The body of the calendar entry in ical file/Ice
Hi Richard,
thanks for your detailed account on The Debian Way.
Richard Lawrence writes:
> If introducing a dependency on cl-lib right now
> will be the best thing for Org, I have no real objections; if it can be
> put off for a while without significant cost, that would be great, but
> it isn'
Hi Nick and Nicolas,
can we move forward on this patch? It is good, modulo Nicolas
suggestions, which seems good to me.
> This raises an interesting question. What do we do with derived
> back-ends? E.g., what should happen if TYPE is handled in
> `org-link-protocols' for `html' but not `md'?
I
Andreas Leha writes:
> Charles Berry writes:
>
>> Andreas Leha med.uni-goettingen.de> writes:
>>
>>>
>>> Hi Michael,
>>>
>>> Michael Weylandt gmail.com> writes:
>>>
>>> > Hi,
>>> >
>>> > I want to put a summary of my analysis at the beginning of a document
>>> > using results calculated at
Hi Eli,
Eli Zaretskii writes:
> I fixed expand-file-name (trunk revision 116624).
Thanks.
> I'm keeping the bug open until the Org part is either fixed or we
> decide it doesn't need fixing.
In my opinion, it needs a fix, but it's quite a rewrite, so don't
expect any change here before Org 9.
Hi Michael,
thanks for the patch.
Pontus Michael writes:
> Primary reason for this change is to fix the problem which I describe
> as
> follows:
>
> This function is not 100% compatible with a org-edit-src facility,
> which provides an option to have indentation added to the code inside
> the b
Hi,
Boyd Kelly writes:
> But when I run: emacs -l ~/.emacs -eval '
> (org-export-icalendar-all-agenda-files)' --batch
^
This function does not exist in the current distribution of Org,
and the problem does not exist in this distribution AFAIK.
If you can
Hello,
I have several sections in my "review" agenda that I try to make empty
("Tasks to refile", "Tag me", "Stuck Projects", ...). Is it possible to
avoid displaying the section title when it does not have any contents?
Thanks,
Alan
Hi Nicolas,
Nicolas Goaziou writes:
> This needs to be properly defined.
>
> Where protecting characters in verbatim parts of the buffer should
> happen? Within footnotes only? In every verbatim part? And on which
> characters?
AFAIK in footnotes only, for the # ^ ! & characters (% is already
e
Hi all,
let's finally close this thread, thanks all for your inputs.
The solution I suggest is this:
1. implement multi-links opening when C-c C-o is called in a
paragraph and there is no link at point (similar behavior
than the one we have for links in headlines);
2. let `org-open-at-poi
Hi Alan,
On 2014-03-21 at 04:29, Alan Schmitt wrote:
> Hello,
>
> I have several sections in my "review" agenda that I try to make empty
> ("Tasks to refile", "Tag me", "Stuck Projects", ...). Is it possible to
> avoid displaying the section title when it does not have any contents?
>
I think the
Hi Nicolas and Alan,
Nicolas Goaziou writes:
> We first need to know what is the problem. Does Org allow newline
> characters in verbatim objects?
I'd say it should, yes. Otherwise it creates an exception that is
hard to justify, since this exception is linked to only one export
backend.
>
Hi Nicolas,
Nicolas Goaziou writes:
> What about excluding most tempting locations instead?
I pushed a change, mixing this suggestion and the suggestion
to be more explicit about where it is allowed:
http://orgmode.org/cgit.cgi/org-mode.git/commit/?id=343a6dd0
Luke, let's us know if it is cle
Hi Alan and Ken,
Ken Mankoff writes:
> I think the answer is "no" based on the replies to me asking this
> exact same question last June:
> https://lists.gnu.org/archive/html/emacs-orgmode/2013-06/msg00681.html
Yes, it is not possible, but highly desirable.
On top of my TODO list.
--
Bastie
* Yasuhito Takamiya wrote:
> Hello all,
Hi!
Short remark:
> - [l] Later Today
> - [e] This Evening
> - [t] Tomorrow
> - [w] This Weekend
> - [n] Next Week
> - [i] In a Month
>From a mnemonic point of view, I would rather choose [m] for "in a
month".
--
mail|git|SVN|photos|postings|SMS|phonec
Hi,
Bastien writes:
> Hi Alan and Ken,
>
> Ken Mankoff writes:
>
>> I think the answer is "no" based on the replies to me asking this
>> exact same question last June:
>> https://lists.gnu.org/archive/html/emacs-orgmode/2013-06/msg00681.html
Sorry, I did not remember this conversation. Thank y
Hello,
When using this minimal configuration:
--8<---cut here---start->8---
(setq org-agenda-prefix-format
'((agenda . " %-11s%i %-12:c%?-12t%7e ")
(timeline . " % s")
(todo . " %i %-12:c")
(search . " %i %-12:c")
(
Resending this as it did not make it to the list. (Is there a way to
make sure that mail that makes it to the list through gmail gets
a reply address to the list?)
Alan Schmitt writes:
> Bastien writes:
>
>>> If it does, what backends do not support it?
>>
>> Only the LaTeX backend.
>>
>> I fix
Hi all!
What I want to do is to generate image (better to say a path to an image)
in the org-file and then see it posted in my blog.
For example, I have such block:
#+BEGIN_SRC text2image :exports results
Foo
Bar
Baz
#+END_SRC
There is text2image command line utility which takes a text and con
i find you have to toggle the inline images (org-toggle-inline-images) two
times to do that. once to turn the old images off, and once to turn them
all back on.
C-c C-x C-v runs that command for me.
John
---
John Kitchin
Associate Professor
Doherty Hall A207F
Depa
Hi Sébastien,
fixed, thanks,
--
Bastien
Hi,
> From a mnemonic point of view, I would rather choose [m] for "in a
> month".
Ah I totally agree && fixed in the latest release.
Thank you very much for your comments.
Yasuhito
On Fri, Mar 21, 2014 at 7:03 PM, Karl Voit wrote:
> * Yasuhito Takamiya wrote:
>> Hello all,
>
> Hi!
>
> Short
Hi Nicolas,
I cannot follow the link here:
* Définition
[[*D%C3%A9finition][Définition]]
it asks me to create a headline. The link has been stored t
Hello Alan,
> It would be great to be able to configure some of the hard-coded dates
> and time, such as:
> - later today: number of hours (currently 3)
> - start of evening: currently 18:00
> - start of day: currently 08:00
> - start of weekend: currently Saturday (you could use
> `org-agenda-w
Hi Bastien,
thanks for getting back to this. Meanwhile I can live with exporting the
whole agenda to ics.
Am 21.03.2014 09:03, schrieb Bastien:
Hi,
"G. Martin Butz" writes:
While importing and viewing one of my org files, I do get strange results:
+ I only see dates from DONE-entries
+ T
Hi Martin,
thanks for the details, good to know part of the bug is gone.
"G. Martin Butz" writes:
> I checked with the file I tested in February with. I now do get active
> TODO-entries. No idea what I changed meanwhile. But I also get entries
> for the DONE-state, which I do not want.
The def
Hi all (and devs;)),
what about adding #+HOMEPAGE (alongside #+AUTHOR and #+EMAIL) to the
metadata? What are the pros and cons? (One argument against: default
LaTeX classes do not support this. Any other?)
Regards,
--
Marcin Borkowski
http://octd.wmi.amu.edu.pl/en/Marcin_Borkowski
Adam Micki
Hi all!
I have such block:
#+BEGIN_SRC my-python
import sys
sys.platform
#+END_SRC
I want it to be with syntax highlighting, so it will looks like (in a
org-file) exactly as:
#+BEGIN_SRC python
import sys
sys.platform
#+END_SRC
(of course the value of org-src-fontify-natively is t).
but in t
Hello,
Bastien writes:
> can you repost the patch by creating another thread with [PATCH]
> in the subject line, and using plain text instead of HTML format?
>
> If you don't use plain text email, simply attach the patch instead
> of including it in the body of the email.
>
> Nicolas, I'll let y
Hi Nicolas,
Nicolas Goaziou writes:
> I think this patch is already in master.
Indeed, sorry for the noise,
PS: let's confirm on the list when a patch gets applied, that
helps archiving threads faster.
--
Bastien
Hi Marcin,
Marcin Borkowski writes:
> what about adding #+HOMEPAGE (alongside #+AUTHOR and #+EMAIL) to the
> metadata?
What would it do?
> What are the pros and cons? (One argument against: default
> LaTeX classes do not support this. Any other?)
Not sure what "supporting" means :)
--
Ba
Hello,
Bastien writes:
> let's finally close this thread, thanks all for your inputs.
I'm still waiting for Carsten's input, as I need to know whether
introducing the parser in core functions is a goal for Org or not.
Regards,
--
Nicolas Goaziou
Am 21.03.2014 13:25, schrieb Bastien:
[...]
The default value of `org-export-with-tasks' is `t', which will export
all tasks. You can narrow to not-done tasks with:
(setq org-export-with-tasks 'todo)
Ah, thanks. I studied all the ical export settings, that's why I missed
this generic
Hello,
Bastien writes:
> I cannot follow the link here:
>
>
> * Définition
>
> [[*D%C3%A9finition][Définition]]
>
>
> it asks me to create a headline.
Nicolas Goaziou writes:
> Fixed, with tests. Thank you.
Thanks a lot for the quick fix !
--
Bastien
Hello,
Bastien writes:
> Bastien writes:
>
>> Can you make the change (ie. radio-link is a link with a description,
>> the description being its parsed path)? If so, do you want me to make
>> the change in the backends or do you want to take care of this too?
>
> I see you reverted related com
I think already 'supported' in the sense that something like #+HOMEPAGE:
would count as being an in-buffer setting as described in the
http://orgmode.org/manual/In_002dbuffer-settings.html
Org mode uses special lines in the buffer to define settings on a per-file
basis. These lines start with a '#
Hi Nicolas,
Nicolas Goaziou writes:
> For example, `org-make-target-link-regexp' generates a regexp enclosed
> within "\\<...\\>". Unfortunately, that will not match a radio link
> starting with an entity, e.g., <<<\alpha-test>>> \alpha-test. It is
> probably due to the fact that radio targets w
Hi all,
I'm getting a weird problem with orgmode and flyspell mode. Using the
latest version of org from git, open the attached file test.org and run M-x
flyspell-mode, emacs will lock up. It has something to do with tables.
Alternatively, make a new (empty) org file, run flyspell-mode, and start
> From: Sebastien Vauban
> Date: Fri, 21 Mar 2014 14:58:19 +0100
>
> Sebastien Vauban wrote:
> > Today, 2 to 3 new infloops when editing in Org (but that's one of the
> > two things I do: either be in Gnus, or in Org).
> >
> > Org-mode version 8.2.5h (release_8.2.5h-818-g0de200)
> >
> > I did n
> Still no prompt but Emacs survived this infloop (not an infloop, then)
> after I don't know how much time (but more than a couple of minutes).
Then try to
M-x profiler-start RET RET
<... reproduce ...>
M-x profiler-report RET
And the C-u RET on the + to expand the display.
Stefan
Hello,
It seems that ob-ocaml does not support ":results output". For instance,
evaluating the following block:
#+begin_src ocaml :results output
Printf.printf "foo\nbar\n";;
#+end_src
Does not result in the two lines "foo" and "bar" but in the value being
returned.
Unfortunately I don't know e
Aloha all,
I noticed yesterday that a legacy document with this option:
#+OPTIONS: texht:nil
is now broken in a recent Org mode from master.
The following lines now appear in the LaTeX export, when they didn't before:
\hypersetup{
pdfkeywords={},
pdfsubject={},
pdfcreator={Emacs 24.3.1 (O
Thanks for the report. I'm not super familiar with how the texht option
works. I did made the following change base on recommendation from Nicolas
in the :options-alist.
(:latex-hyperref-p nil "texht" org-latex-with-hyperref t)
to
(:latex-hyperref nil nil org-latex-hyperref-template t)
>From Nico
Hello,
t...@tsdye.com (Thomas S. Dye) writes:
> It would be great if the texht option could still be supported.
The equivalent property is no longer a boolean. It can have complex
values, which cannot be set on the OPTIONS line.
> If not, can someone offer advice on the best way to set
> org-l
Bastien writes:
> FWIW, I'd be fine to only allow plain text in radio targets, instead
> of the full syntax. Your take.
It would probably make my life less miserable. But do radio target users
need entities within?
Regards,
--
Nicolas Goaziou
Hi Nicolas,
Nicolas Goaziou writes:
> It would probably make my life less miserable. But do radio target users
> need entities within?
IMHO the best way to know is to open a new thread with [POLL]
and a very clear subject like
"[POLL] Do you need special entities in radio target?"
2 cents,
[Christopher Witte (2014-03-21 15:29:24 UTC)]
> Hi all,
>
> I'm getting a weird problem with orgmode and flyspell mode. Using the
> latest version of org from git, open the attached file test.org and run M-x
> flyspell-mode, emacs will lock up. It has something to do with tables.
There is a thr
Dear org-mode list,
I’m having a problem with org-mode source blocks in python when python-mode.el
is enabled for python-mode instead of python.el.
I detailed my problem here:
http://stackoverflow.com/questions/22565379/emacs-org-mode-python-source-blocks-dont-export-with-python-mode-el
and it
Hello,
moving lot of stuff to Emacs/org-mode and would like to find some
better way for generating quotes/invoices for our small/freelancer
company. FOund out about org-invoice and wonder whether it's still
alive and whether it can fully replace some php/mysql app I use atm
for generating quotes/i
Nicolas Goaziou writes:
>> If not, can someone offer advice on the best way to set
>> org-latex-hyperref-template to achieve the same file-local effect?
>
> Assuming `org-export-allow-bind-keywords' is non-nil, does
>
> #+BIND: org-latex-hyperref-template ""
>
> work?
I can't get this to work.
Or perhaps to survey what is already out there. What are people already
doing/trying to do?
On 21 March 2014 18:28, Bastien wrote:
> Hi Nicolas,
>
> Nicolas Goaziou writes:
>
> > It would probably make my life less miserable. But do radio target users
> > need entities within?
>
> IMHO the bes
On Mar 20, 2014, at 21:34, Charles Berry wrote:
> Andreas Leha med.uni-goettingen.de> writes:
>
>>
>> Hi Michael,
>>
>> Michael Weylandt gmail.com> writes:
>>
>>> Hi,
>>>
>>> I want to put a summary of my analysis at the beginning of a document
>>> using results calculated at the end of
Hi Nicolas,
Nicolas Goaziou writes:
> Matt Lundin writes:
>
>> The rewrite of org-mode-flyspell-verify in commit
>> 4a27c2b4b67201e0b23f431bdaeb6460b31e1394 (Nov 21, 2013) makes navigating
>> org-mode files with large chunks of text very slow.
>
> [...]
>
>> => Org-mode version 8.2.5h (release_
Bastien writes:
> Hi Matt and all,
>
> thanks a lot for the detailed investigation -- I revisited the
> related problems and applied a fix. Please let me know if you
> encoutner some glitches.
Seems to work fine now. Thanks!
Matt
Mail von Bastien, Wed, 19 Mar 2014 at 12:08:47 +0100:
Hello Bastian,
> Yes, I confirm the bug -- by any chance, did you have time to
> sort this out? (I see you already committed a fix to org-bibtex.el)
sorry, just saw your reply.
I will get into it and try to make a proposal.
With kind regar
Bastien wrote:
> Eli Zaretskii writes:
>
>> I hope Org maintainers could take a good look on this.
>
> Yes, I think Nicolas is on it.
>
> Speaking of that, this is one of the few remaining bugs
> we want to fix before 8.2.3, I hope we will have time to
> merge 8.2.3 into the emacs-24 branch then.
Hello,
It appears that org-mode produces invalid latex code. An example
follows.
Best,
Kosta
Insert the following example text into an org buffer:
===
* _Example Text_
===
Then export as latex. The following is produced:
===
% Created 2014-03-21 Fri 17:45
\documentclass[11pt]{article}
\usepac
Dnia 2014-03-21, o godz. 14:07:58
Bastien napisał(a):
> Hi Marcin,
>
> Marcin Borkowski writes:
>
> > what about adding #+HOMEPAGE (alongside #+AUTHOR and #+EMAIL) to the
> > metadata?
>
> What would it do?
>
> > What are the pros and cons? (One argument against: default
> > LaTeX classes d
t...@tsdye.com (Thomas S. Dye) writes:
> Nicolas Goaziou writes:
>
>>> If not, can someone offer advice on the best way to set
>>> org-latex-hyperref-template to achieve the same file-local effect?
>>
>> Assuming `org-export-allow-bind-keywords' is non-nil, does
>>
>> #+BIND: org-latex-hyperref
On 3/20/14, Bastien wrote:
>> my strong intuition says that it calls for a global solution rather
>> than patching each one as it comes up.
>
> There is this bug report I made recently:
> http://comments.gmane.org/gmane.emacs.bugs/83721
interesting. these topics are worth looking at.
as for org
hi bastien,
thanks for revisiting this.
i cannot do thorough bug reports at this time, but there are a few
undo-related issues in org-mode now. here are a few from memory
[there are others]:
- occasional buffer or undo-tree corruption from c-c ' [see previous
posts in this thread]
- disrupt
Noah Slater writes:
> Or perhaps to survey what is already out there. What are people
> already doing/trying to do?
I opened a different thread to make the poll more prominent.
--
Bastien
Hi all,
the subject says it all -- see this thread for reference:
http://thread.gmane.org/gmane.emacs.orgmode/83648
Would you be okay if radio targets like <<>>
are limited to plain text?
Thanks for your feedback,
--
Bastien
imo radio targets are fundamentally limited because they only work in
the same file, while org has become a multi-file mode. i am ok with
cosmetic limitations in addition.
--
The Kafka Pandemic: http://thekafkapandemic.blogspot.com
The disease DOES progress. MANY people have died from it. And
Aloha Nick,
Nick Dokos writes:
> #+BIND is supposed to bind the variable *during export*. The test is to
> run the export and see if the hyperref stuff is gone from the tex file.
>
> Nick
I did run the export and the hyperref stuff was still in the tex file.
I'm exporting asynchronously--perha
Hi all,
export to markdown has a strange problem. Before the markdown
contents, I get a ToC in HTML. #+OPTIONS: toc:nil disables that, but I
guess it shouldn't be needed.
Org-mode version 8.2.5f
(8.2.5f-elpa @ /home/marcin/.emacs.d/elpa/org-20140116/)
Best,
--
Marcin Borkowski
http://octd.wm
"Stefan-W. Hahn" writes:
> I will get into it and try to make a proposal.
Thanks in advance!
--
Bastien
Hi Samuel,
Samuel Wales writes:
> typical example of last one:
>
> ===
> * bastien
> #+begin_src org
> bastien
> ^bastien
> #+end_src
> * bastien
> ===
>
> put point at ^, fill-paragraph, undo. with undo-tree, at least, the
> buffer will be corrupted.
Not for me. This has surely to do wit
Samuel Wales writes:
> as for org contexts, perhaps we need something like an
> org-show-canonical-form, where canonical form is a state of visibility
> that can be created from a folded org file using TAB and arrow keys
> alone.
You mean `org-reveal' should depend on the some hardcoded visibili
Thomas,
Thomas S. Dye wrote:
Aloha Nick,
Nick Dokos writes:
#+BIND is supposed to bind the variable *during export*. The test is to
run the export and see if the hyperref stuff is gone from the tex file.
Nick
I did run the export and the hyperref stuff was still in the tex file.
I'm expo
t...@tsdye.com (Thomas S. Dye) writes:
> Aloha Nick,
>
> Nick Dokos writes:
>
>> #+BIND is supposed to bind the variable *during export*. The test is to
>> run the export and see if the hyperref stuff is gone from the tex file.
>>
>> Nick
>
> I did run the export and the hyperref stuff was still
hi bastien,
On 3/21/14, Bastien wrote:
>> buffer will be corrupted.
>
> Not for me. This has surely to do with undo-tree.
in emacs 23, i get the same bug with built-in undo.
>> one thing org sometimes does is try to set buffer-undo-list. it's
>> really for speed imo. i can't think of any rea
s/most cases/all cases that i am aware of/
On 3/21/14, Samuel Wales wrote:
> in most cases, i think the undo list manipulation should never happen
> in the first place. it just causes too many problems.
i am saying that i prefer [and i believe new users will often prefer]
that org not hide things unless they are just normal folding. this
preference is currently impossible to convey to org.
===
more details:
i do not ever want to see only the first headline of a set of
headlines, for example.
Hi Konstantin,
Konstantin Kliakhandler writes:
> It appears that org-mode produces invalid latex code. An example
> follows.
Fixed, thanks,
--
Bastien
Hi Samuel,
Samuel Wales writes:
> c-c '
> edit
> c-c '
> edit
> undo
> undo OOPS the source edit is skipped over what just happened?
> c-c '
> undo OOPS the undo changes are all gone where did they go?
The changes happen in different buffers, there is no reason to
expect undo to
Hi Marcin,
Marcin Borkowski writes:
> So the problem is: it would be (imho) useful to have a "homepage" added
> to general metadata, but it is not clear how to translate this to e.g.
> LaTeX's (rather ancient) concept of metadata. (Interestingly, some
> other classes, e.g. memoir, koma-script a
I think I see what you mean but it's hard to implement.
The only way to fix this is to discuss the default value for
org-show-* properties (and maybe some others) -- if you have
suggestions here with examples on how different defaults would
be less confusing, let's discuss this specifically.
In t
Hi Marcin,
Marcin Borkowski writes:
> export to markdown has a strange problem. Before the markdown
> contents, I get a ToC in HTML. #+OPTIONS: toc:nil disables that, but I
> guess it shouldn't be needed.
I guess that's on purpose, since you can use HTML in markdown.
If you don't want the toc
On 3/21/14, Bastien wrote:
> The changes happen in different buffers, there is no reason to
> expect undo to let you undo changes you made from another buffer.
you might be surprised to find that i disagree. :]
let's concentrate on just one aspect of this.
i believe that most users expect that
Hi Mishal,
Mishal Awadah writes:
> I’m having a problem with org-mode source blocks in python when
> python-mode.el is enabled for python-mode instead of python.el.
>
> I detailed my problem here: http://stackoverflow.com/questions/
> 22565379/
> emacs-org-mode-python-source-blocks-dont-export-w
Samuel Wales writes:
> in other words, if b consists of editing a source block, then i
> /still/ expect b to be undone, because the contents of that source
> block are part of mybuffer.org.
I think we are miscommunicating...
I simply say that I cannot reproduce the bug: for me, when b
consists
bug #3:
insert a source block
edit after it
c-c ' to edit
edit
c-c ' to go back to mybuffer
edit before the source block
undo
undo
you should notice that the source block is not restored.
note that this is not the same buffer corruption issue i reported previously.
in that one, you insert a sou
here is the fix for bug #3:
change this line in org-src.el
(let ((buffer-undo-list t))
to:
;; don't change my undo list here, please
(progn
this fixes the problem. i really don't think this kind of fancy undo
list manipulation is the right thing to do in org.
On 3/21/14, S
Dnia 2014-03-22, o godz. 00:44:40
Bastien napisał(a):
> Hi Marcin,
>
> Marcin Borkowski writes:
>
> > So the problem is: it would be (imho) useful to have a "homepage"
> > added to general metadata, but it is not clear how to translate
> > this to e.g. LaTeX's (rather ancient) concept of metad
Dnia 2014-03-22, o godz. 01:00:58
Bastien napisał(a):
> Hi Marcin,
>
> Marcin Borkowski writes:
>
> > export to markdown has a strange problem. Before the markdown
> > contents, I get a ToC in HTML. #+OPTIONS: toc:nil disables that,
> > but I guess it shouldn't be needed.
>
> I guess that's
Marcin Borkowski writes:
> Dnia 2014-03-22, o godz. 00:44:40
> Bastien napisał(a):
>
>> Hi Marcin,
>>
>> Marcin Borkowski writes:
>>
>> > So the problem is: it would be (imho) useful to have a "homepage"
>> > added to general metadata, but it is not clear how to translate
>> > this to e.g. La
I use babel mostly for shell scripts. I wrote a patch to allow toggling the
handling of errors & std err. I prefer standard error just get printed with
everything else, the same as calling a script from a terminal. Doing this
properly
with header arguments etc. has been discussed before (google or
After 243 commits to a constellation of org files, producing 10849 lines of
LaTeX code from the Beamer exporter, which render into 229 pages of
beamerarticle print-ready material, including 156 captioned code listings
(and a handful of un-numbered ones) and 27 pages of fully indexed glossary
entrie
1 - 100 of 102 matches
Mail list logo