Bastien gnu.org> writes:
> Brady Trainor uw.edu> writes:
>
> > For my solution, I changed insert to ignore.
>
> Can you provide your change in the form of a patch?
>
> 4. in Emacs, hit `C-x v =' from the file to create the patch
I wanted to return to this and attempt it, here is my first
Bastien gnu.org> writes:
> ---does the Org version that comes from the maint branch
> still needs a fix? If so, can you describe the problem
> again?
I did test the `maint` branch today. The behavior was not ideal for my
funny use-case.
For `org-insert-heading' (M-RET), I wanted the follow
Dnia 2014-03-27, o godz. 15:43:45
Rainer M Krug napisał(a):
> Brett Viren writes:
>
> > Rainer M Krug writes:
> >
> >> Brett Viren writes:
> >>> file:///path/to/foo.tex.orglink?line=42
> >
> >> But jumping to the .org file would be the aim - right?
> >
> > Yes, right. Maybe a better exampl
Dnia 2014-03-26, o godz. 09:26:15
Rick Frankel napisał(a):
> On 2014-03-23 17:01, Marcin Borkowski wrote:
> > Hi list,
> >
> > publishing doesn't work. I guess that I broke something;). May the
> > source and publishing directories be the same? I have this in my
> > init.el:
> >
> > (setq or
Dnia 2014-03-26, o godz. 18:33:30
Charles Millar napisał(a):
> If I remember to close the first exported PDF, the revised subtree
> exports OK.
>
> I'm just curious, does the problem exist iff the pdf, that is to be
> replaced, is opened?
This is rather a workaround, but don't use Adobe Reade
I'm trying to use o-blog with org-mode-8.2.5h, but the function
org-publish-blog in o-blog requests org-export-as-html. The correct
function is org-html-export-as-html
Is o-blog so unmaintained and should I just look for an alternative?
--
Esben Stien is b0ef@e s a
Hello,
Pretty much what the headline says. This incorrect interpretation means
that if for example one tries to use org-cdlatex completions in that
line or later in the block, they won't work: Instead, new cells will be
created.
Example code:
\begin{align*}
|x
\end{align*}
Emacs : GNU Emacs 2
Applied, Thanks!
Jakob Lombacher writes:
> When using org-babel with mixed (double, int) input like below, the c file
> was not written correctly. The numbers where left out and only the commas
> where written.
>
> I guess it was a typo. Attached is the patch.
>
> Jakob
>
> ---
>
> #+RESULTS[88
Alan Schmitt writes:
> Nicolas Goaziou writes:
>
>> I suggest to use the dedicated MATCH argument for `org-map-entries':
>>
>> (defun as/delete-ignored-heading (backend)
>> "Remove every headline with a tag `ignoreheading' in the
>> current buffer. BACKEND is the export back-end bein
Hi,
Nicolas Goaziou writes:
> As you may know, `org-element-context' returns the object under point,
> according to Org Syntax. The questions are: should it be a little
> sloppy, for convenience? And, if it should, what degree of sloppiness is
> acceptable?
Would it make sense to make it option
I've attached patch below, but I'm affraid that there is something wrong
with indentation.
I'm not sure if there is problem with my settings or just entire
ox-html.el is indented badly.
I've been trying to indent file with the default parameters.
I started Emacs with -Q parameter and as I can see
On my Win7 + MSYS + MinGW + MikTex I found a texinfo 4.13 that compiled
without complaints about UTF-8. I suppose the problem is faced mostly by
Mac users.
Unfortunately I can't reproduce the problem here, so I have no clue about
the contents of the .info output...
Kindest regards, Andrea
Il gior
When using org-babel with mixed (double, int) input like below, the c file
was not written correctly. The numbers where left out and only the commas
where written.
I guess it was a typo. Attached is the patch.
Jakob
---
#+RESULTS[8894f01ba8e219bd6cafb49748f4d5cad8bb6fd1]: test-parameter
|
Hi Pascal,
This looks like a good patch. If I could make three changes/requests.
1. This patch should also work for "begin_src bash" code blocks. After
a very quick glance it doesn't appear to.
2. Could you include one or two tests ensuring that this patch does what
it intends with bash
Rainer M Krug writes:
> Eric Schulte writes:
>
>> Rainer M Krug writes:
>>
>>> Eric Schulte writes:
>>>
Rainer M Krug writes:
> Eric Schulte writes:
>
>> Charles Berry writes:
>>
>>> John Hendy gmail.com> writes:
>>>
>>> [deleted]
>
>
Nicolas Goaziou writes:
> Hello,
>
> Alan Schmitt writes:
>
>> Have there been recent changes regarding the "COMMENT" keyword and
>> tangling? I just saw some blocks whose grand parent is a comment being
>> tangled in my configuration file.
>
> This should be fixed. Thank you.
Thanks, I confirm
Hello,
As you may know, `org-element-context' returns the object under point,
according to Org Syntax. The questions are: should it be a little
sloppy, for convenience? And, if it should, what degree of sloppiness is
acceptable?
Note that, at the time being, the function is already somewhat slopp
Hello,
Alan Schmitt writes:
> Have there been recent changes regarding the "COMMENT" keyword and
> tangling? I just saw some blocks whose grand parent is a comment being
> tangled in my configuration file.
This should be fixed. Thank you.
Regards,
--
Nicolas Goaziou
Nick Dokos writes:
> Rainer M Krug writes:
>
>
>> calling
>>
>> ,
>> | emacs +42 foo.org
>> `
>>
>> should open the file foo.org and put the cursor in line 42.
>>
>
> In most cases, it would be better to use emacsclient, otherwise
> you might end up with many emacs instances; but more i
Rainer M Krug writes:
> calling
>
> ,
> | emacs +42 foo.org
> `
>
> should open the file foo.org and put the cursor in line 42.
>
In most cases, it would be better to use emacsclient, otherwise
you might end up with many emacs instances; but more importantly
perhaps, using emacsclient
Brett Viren writes:
> Rainer M Krug writes:
>
>> Brett Viren writes:
>>> file:///path/to/foo.tex.orglink?line=42
>
>> But jumping to the .org file would be the aim - right?
>
> Yes, right. Maybe a better example is:
>
> file://foo.orglink?line=42
calling
,
| emacs +42 foo.org
`
Andrea Rossetti writes:
> Rainer M Krug krugs.de> writes:
>
> ...
>> This is the version info - I did not install an old one on my mac:
>>
>> ,
>> | $ makeinfo --version
>> | makeinfo (GNU texinfo) 4.8
>> |
>> | Copyright (C) 2004 Free Software Foundation, Inc.
> ...
>
> I guess the texinf
Hello,
Have there been recent changes regarding the "COMMENT" keyword and
tangling? I just saw some blocks whose grand parent is a comment being
tangled in my configuration file.
Here is an ECM. If you `org-babel-load-file' this file:
--8<---cut here---start->
Rainer M Krug writes:
> Brett Viren writes:
>> file:///path/to/foo.tex.orglink?line=42
> But jumping to the .org file would be the aim - right?
Yes, right. Maybe a better example is:
file://foo.orglink?line=42
which might get interpreted as "go to line 42 in ./foo.org".
This example is
Nicolas Goaziou writes:
> I suggest to use the dedicated MATCH argument for `org-map-entries':
>
> (defun as/delete-ignored-heading (backend)
> "Remove every headline with a tag `ignoreheading' in the
> current buffer. BACKEND is the export back-end being used, as
> a symbol."
>
Rainer M Krug krugs.de> writes:
...
> This is the version info - I did not install an old one on my mac:
>
> ,
> | $ makeinfo --version
> | makeinfo (GNU texinfo) 4.8
> |
> | Copyright (C) 2004 Free Software Foundation, Inc.
...
I guess the texinfo version is too old for UTF-8: you may see
Andrea Rossetti writes:
> Rainer M Krug krugs.de> writes:
>
>>
> ...
>> | makeinfo --no-split org.texi -o org
>> | org.texi:15: warning: unrecognized encoding name `UTF-8'.
>> `
>>
>> Is this something in my setup? Should I worry?
>
> My guess: could it be that you have an old version
> of
Rainer M Krug krugs.de> writes:
>
...
> | makeinfo --no-split org.texi -o org
> | org.texi:15: warning: unrecognized encoding name `UTF-8'.
> `
>
> Is this something in my setup? Should I worry?
My guess: could it be that you have an old version
of makeinfo/texinfo, not supporting UTF-8 fo
Hello,
Is there a public function that can accept a string such as "3/4/5" (US
Format) and normalize it to [2005-03-04 Fri]?.
I need it for a bit of helper code.
Thanks,
Mirko
Alan Schmitt writes:
> Thanks a lot for the suggestion, here is what I ended up doing:
>
> #+begin_src emacs-lisp
> (defun as/delete-ignored-heading (backend)
> "Remove every headline with a tag `ignoreheading' in the
> current buffer. BACKEND is the export back-end being used, as
> a s
Hello Nicolas,
Nicolas Goaziou writes:
> Hello,
>
> Alan Schmitt writes:
>
>> I've been playing with block chaining to generate some dot file then to
>> export then as images. I had a little trouble finding the number of '\'
>> I need to put in front of a quote if I want the quote to be quoted.
Nicolas Goaziou writes:
> Hello,
>
> Alan Schmitt writes:
>
>> I need to ignore a heading during a LaTeX export (I don't want the
>> "section" command to be generated, but I need the text to be included;
>> the heading is there because the previous one is tagged with "export").
>> I found this s
Hi
I get the following warning when using make in my org-git:
,
| $ make
| .
| .
| .
| Done (Total of 108 files compiled, 3 skipped)
| /Applications/Xcode.app/Contents/Developer/usr/bin/make -C doc info
| org-version: 8.2.5h (release_8.2.5h-864-g3e5fc4)
| makeinfo --no-split org.texi -o org
|
Sebastien Vauban
writes:
> Could you explain why you would choose a hook? What's guiding your
> choice?
The fact that I work in the Org buffer and can use `org-map-entries',
which trivializes the problem here. OTOH, a filter works at the LaTeX
code level and ignoreheading tag may be missing (
Hi Charles,
> First, I have subsequent messages in this thread and the discussion.
>
> Should Nick's observation, that
>
>> IOW, it cannot tell the difference between a successful export and an
>> export failure with an already existing PDF
>
>
> also include the qualification that the existing PD
Nicolas Goaziou wrote:
> Alan Schmitt writes:
>
>> I need to ignore a heading during a LaTeX export
>
> You can use a hook or a filter to remove the headline. I would use
> a hook in this case.
Could you explain why you would choose a hook? What's guiding your
choice?
Thanks!
> See (info "(org
Hello,
Nicolas Goaziou wrote:
> Sebastien Vauban writes:
>
>> FWIW, I'm using this in some export code I have:
>>
>> (let* ((orgfile (buffer-file-name))
>> (base-name (file-name-base orgfile))
>> (htmlfile (concat base-name ".html"))
>> (pdffile (concat
Hi Nicolas,
>>> IOW, it cannot tell the difference between a successful export and an
>>> export failure with an already existing PDFFILE.
>>
>> This is not true as this code checks for the `errors' variable in all
>> cases. With an already existing PDFFILE, you will end up with this
>> message:
Hello,
Sebastien Vauban
writes:
> FWIW, I'm using this in some export code I have:
>
> (let* ((orgfile (buffer-file-name))
> (base-name (file-name-base orgfile))
> (htmlfile (concat base-name ".html"))
> (pdffile (concat base-name ".pdf")))
>
Hi Sébastien,
Sebastien Vauban
writes:
> Some time ago, the "flowing text" inside Org buffers was rendered in the
> `org-default' face.
>
> It isn't the case anymore. Is it a bug on my side?
You can turn the use of the 'org-default face on with
M-x buffer-face-mode RET
Using buffer-face-mod
Hi Karl,
Karl Voit writes:
> I am using custom links like "[[photo:FirstnameLastname.jpg]]" in my
> contacts.org.
>
> Those links stopped working recently. Whenever I try to click or C-c
> C-c the link, I get "user-error: No link found".
This is a known issue, related to the recent rewrite of
`
Brett Viren writes:
> Nick Dokos writes:
>
>> One more (half-)possibility is as follows: produce the tex file and
>> compile it not with pdflatex, but with plain latex, producing a DVI
>> file. Passing the -src option to the latex invocation inserts "source
>> specials" into the DVI file that so
Suvayu Ali writes:
> On Thu, Mar 27, 2014 at 09:18:43AM +0100, Rainer M Krug wrote:
>> Suvayu Ali writes:
>>
>> > On Tue, Mar 25, 2014 at 11:07:54AM +0100, Rainer M Krug wrote:
>> >> Hi
>> >>
>> >> I am working on a longish document which will be converted to pdf, and I
>> >> am doing debuggin
On Thu, Mar 27, 2014 at 09:18:43AM +0100, Rainer M Krug wrote:
> Suvayu Ali writes:
>
> > On Tue, Mar 25, 2014 at 11:07:54AM +0100, Rainer M Krug wrote:
> >> Hi
> >>
> >> I am working on a longish document which will be converted to pdf, and I
> >> am doing debugging of scripts at the moment.
>
Hello,
Alan Schmitt writes:
> I need to ignore a heading during a LaTeX export (I don't want the
> "section" command to be generated, but I need the text to be included;
> the heading is there because the previous one is tagged with "export").
> I found this solution:
>
> https://stackoverflow.c
Hello,
Grant Rettke writes:
> Sacha Chua made a nice hack to export checkboxes as unicode symbols to
> HTML here:
>
> http://sachachua.com/blog/2014/03/emacs-tweaks-export-org-checkboxes-using-utf-8-symbols/?shareadraft=baba27119_533313c944f64
>
> (defun sacha/org-html-checkbox (checkbox)
> "F
Hello,
I need to ignore a heading during a LaTeX export (I don't want the
"section" command to be generated, but I need the text to be included;
the heading is there because the previous one is tagged with "export").
I found this solution:
https://stackoverflow.com/questions/10295177/is-there-an-
Suvayu Ali writes:
> On Tue, Mar 25, 2014 at 11:07:54AM +0100, Rainer M Krug wrote:
>> Hi
>>
>> I am working on a longish document which will be converted to pdf, and I
>> am doing debugging of scripts at the moment.
>>
>> Therefore I export the document to pdf, and look for errors there. Now I
Charles Berry writes:
> Rainer M Krug krugs.de> writes:
>
>>
>>
>> The subject says it all - when I set
>>
>> #+PROPERTY: eval never-export
>>
>> the interactive evaluation of R code blocks is disabled. Message:
>>
>> Evaluation of this R code-block is disabled.
>>
> [rest deleted]
>
> I
49 matches
Mail list logo
