Myles English mylesengl...@gmail.com writes:
Myles English writes:
Nicolas Goaziou writes:
One option could be to define a specialized latex back-end dedicated to
moderncv class, much like ox-koma-letter.el does for scrlttr2.
I did actually make a start on this, I'll dig it out and put it
Subhan Michael Tindall wrote:
I have the following agendas (among others) defined:
(x Last worked ((alltodo ( (org-agenda-sticky nil)
(org-agenda-sorting-strategy (quote (tsia-up
todo-state-down)))
(y Last worked2 ((tags LastWorked={.+} (
(org-agenda-sticky nil)
Hello Nicolas,
On Mo, 2014-09-22 at 17:29 +0200, Nicolas Goaziou wrote:
FWIW, I cannot reproduce it.
This was quite painful to isolate, but I’ve now identified a minimal
configuration which should trigger this bug.
──
;; BEGIN
Hi, is it possible that these function cause the buffer automatically
scrolling when saving?
When I save My buffer jumps/scrolls up so that my cursor is on the last row
on my screen.
Greets
2014-09-11 23:55 GMT+02:00 Adriaan Sticker adriaan.stic...@gmail.com:
Cool, thanks!
2014-09-11 18:28
Nicolas Goaziou m...@nicolasgoaziou.fr writes:
[...]
`org-html-publish-to-html' is not meant to be called directly, but
rather used in a project definition as a :publishing-function value.
Speaking of which, why don't you simply create a proper project-alist
and call `org-publish' on it
Rainer M Krug rai...@krugs.de writes:
Thanks for the summary Rainer.
I think that org could be a perfect environment for building CVs if
one could come up with an HOWTO and many examples how to do it - and I
think this is going into the right direction.
I think the right approach is cooking
On Wed, 17 Sep 2014 09:29:48 +, Tobias Getzner wrote:
On Wed, 17 Sep 2014 08:27:21 +, Tobias Getzner wrote:
When using LaTeX-based export targets that produce a .tex file as output
(export to LaTeX file, PDF, PDF and open), I receive the message «Buffer
foo.tex modified; kill
Rasmus ras...@gmx.us writes:
Hi,
Rainer M Krug rai...@krugs.de writes:
Thanks for the summary Rainer.
Hope I didn't forget anything...
I think that org could be a perfect environment for building CVs if
one could come up with an HOWTO and many examples how to do it - and I
think this
Hi Aaron,
Aaron Ecay wrote:
2014ko abuztuak 29an, Sebastien Vauban-ek idatzi zuen:
I think it's related to an Emacs bug (#16440) which I reported on the
Org mailing list in February.
I don’t completely understand what is going on in that bug report. My
proposal is to convert org-copy-face
On Tue, 23 Sep 2014 10:22:45 +0200, Tobias Getzner wrote:
This was quite painful to isolate, but I’ve now identified a minimal
configuration which should trigger this bug.
──
;; BEGIN minimal.el
(add-to-list 'load-path
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 List,
seems it was renamed to
,[ C-h v org-planning-or-clock-line-re RET ]
| org-planning-or-clock-line-re is a variable defined in `org.el'.
| Its value is [...]
| Documentation:
| Matches a line with planning info.
| Matched keyword is in group 1.
`
Calling 'org-element-at-point
Thorsten Jolitz tjol...@gmail.com writes:
sorry for the noise, and Emacs restart fixed the issue.
Hi List,
seems it was renamed to
,[ C-h v org-planning-or-clock-line-re RET ]
| org-planning-or-clock-line-re is a variable defined in `org.el'.
| Its value is [...]
| Documentation:
|
When mark-up such as =monospace=, /italic/, etc. is preceded by a
non-8bit whitespace, e. g., «narrow no-break space» (U+202F) or «no-break
space» (U+00A0), org-mode will not recognize the mark-up content
correctly; i. e., this content will fail to be syntax-highlighted, and
the mark-up syntax
Hello all,
since eww comes bundled with Emacs nowadays it feels natural to be able
store a link to the current url of an eww buffer. This functionality
has already been in place for w3m for a while.
Find a respective patch attached. I hope the fact that the patch is
attached is acceptable as
Jorge A. Alfaro-Murillo wrote:
Perhaps I am biased because I learned LaTeX and BibTeX before
Org, but I think that for references BibTeX (plus a little bit
of emacs configuration) has everything I could need. I guess if
you are more used to Org, it might be worth to invest time and
come up
On Thu, Sep 18, 2014 at 2:49 PM, Gary Oberbrunner ga...@oberbrunner.com
wrote:
On Thu, Sep 18, 2014 at 12:23 PM, Subhan Michael Tindall
subh...@familycareinc.org wrote:
Lists are very explicitly not intended to contain TODO items.
Checkboxes provide a bit of this functionality, sort of
Dear all,
I just wrote under the subject “Re: Managing articles in org mode
and collaboration”. This posting puts the other one in a broader
context.
While thinking about organizing articles, I asked myself: Wouldn’t
it be useful to keep metadata/notes about *various* kinds of
Christoph Groth writes:
But not all is good:
- Scaling: Some simple tests seem to indicate that org mode
becomes too sluggish with files of about 50k lines. This is a
dimension that could be easily reached over 10 years if the
file grows by 20 lines per day on average. This is not
-Original Message-
From: emacs-orgmode-bounces+subhant=familycareinc@gnu.org
[mailto:emacs-orgmode-bounces+subhant=familycareinc@gnu.org] On
Behalf Of Sebastien Vauban
Sent: Tuesday, September 23, 2014 12:57 AM
To: emacs-orgmode@gnu.org
Subject: Re: [O] [ Bug] tsia-{up,
Aaron may I trouble you to add a flag so that if such errors occur
then the export fails?
From my perspective, if the document doesn't compile, then nothing
should succeed.
Compile includes export from my perspective.
On Mon, Sep 22, 2014 at 10:25 PM, Aaron Ecay aarone...@gmail.com wrote:
Hi
Hi Tobias,
2014ko irailak 23an, Tobias Getzner-ek idatzi zuen:
When mark-up such as =monospace=, /italic/, etc. is preceded by a
non-8bit whitespace, e. g., «narrow no-break space» (U+202F) or «no-break
space» (U+00A0), org-mode will not recognize the mark-up content
correctly; i. e.,
Hi Marco,
Thanks for your patch. TINYCHANGES can only be smaller than 15 lines,
though, and your patch has more than that (even if we discount
boilerplate like the license notice). So you should probably do the
copyright assignment which is described at
Good afternoon,
The ability to org-edit-special inside of source block is truly priceless.
There is a delightful workflow to be found with approach.
It has got me spending more and more time in the edit buffer though,
wanting to utilize
vc-next-action to initiate a commit. This is not possible
Hi again,
2014ko irailak 23an, Aaron Ecay-ek idatzi zuen:
Hi Marco,
Thanks for your patch. TINYCHANGES can only be smaller than 15 lines,
though, and your patch has more than that (even if we discount
boilerplate like the license notice). So you should probably do the
copyright
Hi Grant,
2014ko irailak 23an, Grant Rettke-ek idatzi zuen:
Aaron may I trouble you to add a flag so that if such errors occur
then the export fails?
From my perspective, if the document doesn't compile, then nothing
should succeed.
Compile includes export from my perspective.
Indeed,
Hi Seb,
2014ko irailak 23an, Sebastien Vauban-ek idatzi zuen:
Hi Aaron,
Aaron Ecay wrote:
2014ko abuztuak 29an, Sebastien Vauban-ek idatzi zuen:
I think it's related to an Emacs bug (#16440) which I reported on the
Org mailing list in February.
I don’t completely understand what is
While I expect that there's no code overlap with macro expansion, I asked
about similar stop on unresolved content behavior with respect to links
here: http://article.gmane.org/gmane.emacs.orgmode/90010/
That discussion died off so I thought I'd bring up the topic again here.
Would it be
Hi Bradley,
2014ko irailak 16an, Brady Trainor-ek idatzi zuen:
I have
(global-set-key (kbd S-C-left) 'shrink-window-horizontally)
(global-set-key (kbd S-C-right) 'enlarge-window-horizontally)
(global-set-key (kbd S-C-down) 'shrink-window)
(global-set-key (kbd S-C-up) 'enlarge-window)
Hello Aaron!
On Tue, 23 Sep 2014 13:03:06 -0400, Aaron Ecay wrote:
2014ko irailak 23an, Tobias Getzner-ek idatzi zuen:
When mark-up such as =monospace=, /italic/, etc. is preceded by a
non-8bit whitespace, e. g., «narrow no-break space» (U+202F) or
«no-break space» (U+00A0), org-mode will
Hi Thorsten,
2014ko irailak 18an, Thorsten Jolitz-ek idatzi zuen:
Hi List,
is there a way to call Org speed-commands [fn:1] with a prefix-arg?
Does not work for me ...
The attached patch should allow this. You can use C-u N X or C-N X (where
N is some digits and X a speed command key).
Hi Aaron,
Aaron Ecay wrote:
2014ko irailak 23an, Sebastien Vauban-ek idatzi zuen:
Aaron Ecay wrote:
2014ko abuztuak 29an, Sebastien Vauban-ek idatzi zuen:
I think it's related to an Emacs bug (#16440) which I reported on the
Org mailing list in February.
I don’t completely understand what
Hi Tobias,
2014ko irailak 23an, Tobias Getzner-ek idatzi zuen:
Hello Aaron!
On Tue, 23 Sep 2014 13:03:06 -0400, Aaron Ecay wrote:
You will need to change the variable org-emphasis-regexp-components; see
the documentation thereof.
Thank you very much! This seems to do it.
Might I
Hello (),
I can't download constants.el from
https://staff.fnwi.uva.nl/c.dominik/Tools/constants/index.html
would you mind to post a copy or another link?
Thanks
Dieter
--
Best wishes
H. Dieter Wilhelm
Darmstadt, Germany
Hi Grant,
2014ko irailak 23an, Grant Rettke-ek idatzi zuen:
Good afternoon,
The ability to org-edit-special inside of source block is truly priceless.
There is a delightful workflow to be found with approach.
It has got me spending more and more time in the edit buffer though,
Hi Tobias,
I can reproduce this.
2014ko irailak 23an, Tobias Getzner-ek idatzi zuen:
Hello Nicolas,
On Mo, 2014-09-22 at 17:29 +0200, Nicolas Goaziou wrote:
FWIW, I cannot reproduce it.
This was quite painful to isolate, but I’ve now identified a minimal
configuration which should
Hello,
On 23 September 2014 14:19, Aaron Ecay aarone...@gmail.com wrote:
Hi Grant,
2014ko irailak 23an, Grant Rettke-ek idatzi zuen:
Good afternoon,
The ability to org-edit-special inside of source block is truly
priceless.
There is a delightful workflow to be found with
Aaron Ecay aarone...@gmail.com writes:
Hi Aaron,
2014ko irailak 18an, Thorsten Jolitz-ek idatzi zuen:
Hi List,
is there a way to call Org speed-commands [fn:1] with a prefix-arg?
Does not work for me ...
The attached patch should allow this. You can use C-u N X or C-N X (where
N is
Hello,
Aaron Ecay aarone...@gmail.com writes:
Thanks for all your feedback. The patch is now applied on master.
Thank you.
I’m confused about how ‘org-latex--wrap-label’ works. It tries to
put \label commands outside of floats. That will yield links that
jump to the preceding section,
Hello,
Aaron Ecay aarone...@gmail.com writes:
Um...but the patch I sent works precisely by defining a macro translator,
which does get called for any unexpanded (because undefined) macros.
Macros are not expected to be seen by export back-ends. It happens when
a macro is undefined, but this
Hi,
Aaron Ecay aarone...@gmail.com writes:
You have two options. Either report an error, as you suggested, or
insert an obnoxious message in the output, e.g., UNKNOWN MACRO, à la
DEFINITION NOT FOUND. for footnote definitions. In any case, this
should happen in org-macro.el, not in the
See the custom commands for the agenda in the manual. You can create a
command to do a search in specific files.
The framework would be splitting your big org file into multiple files
and creating a custom search that search only in those particular
files. Of course you would need to change this
Hi Thorsten,
2014ko irailak 23an, Thorsten Jolitz-ek idatzi zuen:
well, here is some positive feedback - thanks for tackling this!
I tried to port this to outshine.el right away, but can't make it to
work. But this might well be due to the fact that I'm on the console, no
X11.
When I do
Hi Dieter,
The link on the page you linked to is broken, but if you manually change
the URL to the following it works:
https://staff.fnwi.uva.nl/c.dominik/Tools/constants/constants.el
--
Aaron Ecay
Hello,
Jacob Gerlach jacobgerl...@gmail.com writes:
While I expect that there's no code overlap with macro expansion, I asked
about similar stop on unresolved content behavior with respect to links
here: http://article.gmane.org/gmane.emacs.orgmode/90010/
That discussion died off so I
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
Hello,
phillip.l...@newcastle.ac.uk (Phillip Lord) writes:
Okay, I've done it this way. Took a bit of fiddling since I need the
project-alist to work in different configurations (i.e. interactively,
in batch and in batch on a CI machine). Also, the timestamp stuff
confused me -- org was
Aaron Ecay aarone...@gmail.com writes:
Hi Thorsten,
2014ko irailak 23an, Thorsten Jolitz-ek idatzi zuen:
well, here is some positive feedback - thanks for tackling this!
I tried to port this to outshine.el right away, but can't make it to
work. But this might well be due to the fact that
Hi Thorsten,
2014ko irailak 23an, Thorsten Jolitz-ek idatzi zuen:
I get 3 different results trying speed-command ':' with prefix:
1. in Org, when edebugging 'org-set-tags-command', C-u : and C-u 4 :
both result in speed-command
That’s because of the use of last-command-keys-vector,
Aaron Ecay aarone...@gmail.com writes:
Hi Bradley,
2014ko irailak 16an, Brady Trainor-ek idatzi zuen:
I have
(global-set-key (kbd S-C-left) 'shrink-window-horizontally)
(global-set-key (kbd S-C-right) 'enlarge-window-horizontally)
(global-set-key (kbd S-C-down) 'shrink-window)
Hi,
Okay, I hope I got a better patch here. I do — for sure — present
another dreadfully long email! Let's start.
Nicolas Goaziou m...@nicolasgoaziou.fr writes:
#+INCLUDE: file.org::#custom_id :noheadline :lines 3-
Is it `:only-contents' or `:no-headline'? Also :kwd1 :kbd2 value is
Aaron Ecay aarone...@gmail.com writes:
Hi Marco,
Thanks for your patch. TINYCHANGES can only be smaller than 15 lines,
though, and your patch has more than that (even if we discount
boilerplate like the license notice). So you should probably do the
copyright assignment which is described
Hi Rasmus,
2014ko irailak 23an, Rasmus-ek idatzi zuen:
I think he did:
Patch:
From: Marco Wahl marcowahls...@gmail.com
Worg:
14. Marco Wahl
...that’s in the section for tinychange contributors without papers on
file though.
--
Aaron Ecay
When I run follow code, it just work:
#+begin_comment
#+BEGIN_SRC R :results value verbatim drawer
data - list(a=[[./test1.org]],b=[[./test2.org]],c=[[./test3.org]])
c(data$a,data$b,data$c)
#+END_SRC
#+RESULTS:
:RESULTS:
Hi John,
2014ko irailak 20an, John Kitchin-ek idatzi zuen:
Hi all,
I have this ina n org-file:
#+NAME: anatase-tio2-elisp
#+BEGIN_SRC emacs-lisp :var data=supporting-information.org:TiO2-data
(remove-if-not (lambda (x) (string= anatase (nth 1 x))) data)
#+END_SRC
#+RESULTS:
Hi Feng,
2014ko irailak 23an, Feng Shu-ek idatzi zuen:
but when I add a #+PROPERTY, it show error like below, how to deal with
it ? thanks ...
#+PROPERTY: header-args:R :colnames yes :rownames no :exports both
#+BEGIN_SRC R :results value verbatim drawer
data -
56 matches
Mail list logo
