2016-06-17 0:43 GMT+02:00 Nicolas Goaziou :
> Hello,
>
> ...
>
> I guess you are refiling to an empty headline.
Hmmm ... the problem is that there was no chance to specify one.
> Anyway, it is fixed.
Thanks a lot!
Fabrice
On Thu, 16. Jun 12:13, William Denton wrote:
When I use the
For one, there is a ~org-babel-results-keyword~ variable. Also I prefer
src block keywords not to stand out as such:
#+begin_src emacs-lisp
(setcar org-structure-template-alist '("s" "#+begin_src ?\n\n#+end_src" ""))
#+end_src
For me
I gave it another try, and I got it finally!
I have to press C-u and then return (not just C-u),
then the helm menu to chose the citation type pops up
Thanks again,
Andreas
John Kitchin writes:
> Andreas Reuleaux writes:
>
>> But what does not currently work for me (and what used to work):
Hello,
Fabrice Popineau writes:
> I don't know what is the minimal setup to reproduce the problem.
> Basically:
>
> - call capture from Chrome (in my case)
> - select n for note
> - select C-c C-w for org-capture-refile
>
> Here is a backtrace.
[...]
> Debugger entered--Lisp error: (wrong-type
Hello,
Xi Shen writes:
> Please take a look at the updated patch. Changes:
>
> - add ORG-NEWS entry
> - add function declaration
> - add input file template for `mssql' engine to remove the "affected rows"
> tail
Applied. Thank you.
Please consider signing FSF papers if you want to contribute
Hello,
I just pushed changes about how Babel calls (including inline calls) are
evaluated. Basically, they are not treated anymore as an Emacs Lisp
variable, but as virtual Babel source blocks, which can then be executed
with `org-babel-execute-src-block'.
I had to tweak a few tests in the proces
(require 'dash)
#+tblname: tab2
| 1 | a | 3 |
| 2 | b | 4 |
| 3 | c | 6 |
| 4 | d | 7 |
#+BEGIN_SRC emacs-lisp :var c0=tab2[,0] :var c2=tab2[,2]
(-zip-with 'list c0 c2)
#+END_SRC
#+RESULTS:
| 1 | 3 |
| 2 | 4 |
| 3 | 6 |
| 4 | 7 |
Uwe Brauer writes:
>> Uwe Brauer writes:
>
>> See (inf
#+BEGIN_SRC emacs-lisp :var data=example-table[,0]
(mapcar 'list data)
#+END_SRC
#+RESULTS:
| 1 |
| 2 |
| 3 |
| 4 |
Uwe Brauer writes:
>> Uwe Brauer writes:
>
>> See (info "(org) var") in particular the section on "Indexable variable
>> values".
>
>
>> Additionally, an
I believe that, in general, things are case-insensitive in org-mode. Please
do help clarify this if this is wrong.
The only place that I have come across as case-sensitive is the tag system.
If you tag a sub-tree with ':archive:', it will not be archived. The tag
has to be ':ARCHIVE:'.
On Thu, Ju
> Uwe Brauer writes:
> See (info "(org) var") in particular the section on "Indexable variable
> values".
> Additionally, an empty index, or the single character ‘*’, are both
> interpreted to mean the entire range and as such are equivalent to
> ‘0:-1’, as
> Uwe Brauer writes:
> See (info "(org) var") in particular the section on "Indexable variable
> values".
> Additionally, an empty index, or the single character ‘*’,
> are both
> interpreted to mean the entire range and as such are equivalent to
>
>>> "Uwe" == Uwe Brauer writes:
> Hi
> I really never used tag search as provided by the agenda. So today I
> just copied the examples of
> http://orgmode.org/worg/org-tutorials/advanced-searching.html
> * TODO Buy clothes for wedding
:wedding:important:erra
When I use the #+RESULTS is in upper case too. I noticed other people have these keywords in
lower case in examples or config files, so I looked in the manual, which says
[1]
"Org uses option keywords (like #+TITLE to set the title) and environment
keywords (like #+BEGIN_HTML to start a HTML
Hi
I am using GNU emacs 25.1.50 (compiled yesterday) and the latest org
version available in ELPA.
I really never used tag search as provided by the agenda. So today I
just copied the examples of
http://orgmode.org/worg/org-tutorials/advanced-searching.html
* TODO Buy clothes for wedding
On 2016-06-16 16:17, Allan Streib writes:
> Alan Schmitt writes:
>
>> I'm trying to consistently use org-clock, but I'm encountering a big
>> obstacle: task selection. I very often do not start working on a task
>> as I'm in my main org file, so to clock it in I would first need to
>> find it th
On 2016-06-16 15:20, cesar mena writes:
>> I'm trying to consistently use org-clock, but I'm encountering a big
>> obstacle: task selection. I very often do not start working on a task as
>> I'm in my main org file, so to clock it in I would first need to find it
>> there, which is a big enough h
Alan Schmitt writes:
> I'm trying to consistently use org-clock, but I'm encountering a big
> obstacle: task selection. I very often do not start working on a task
> as I'm in my main org file, so to clock it in I would first need to
> find it there, which is a big enough hurdle for me not to do
Alan Schmitt writes:
> [ Unknown signature status ]
> Hello,
>
> I'm trying to consistently use org-clock, but I'm encountering a big
> obstacle: task selection. I very often do not start working on a task as
> I'm in my main org file, so to clock it in I would first need to find it
> there, whic
On 2016-06-16 12:43, Eric S Fraga writes:
> On Thursday, 16 Jun 2016 at 06:24, Alan Schmitt wrote:
>> Hello,
>>
>> I'm trying to consistently use org-clock, but I'm encountering a big
>> obstacle: task selection. I very often do not start working on a task as
>> I'm in my main org file, so to clo
On Thursday, 16 Jun 2016 at 06:24, Alan Schmitt wrote:
> Hello,
>
> I'm trying to consistently use org-clock, but I'm encountering a big
> obstacle: task selection. I very often do not start working on a task as
> I'm in my main org file, so to clock it in I would first need to find it
> there, whi
Hello,
considering the following example:
--
#+NAME: test_fun
#+BEGIN_SRC js
function test_fun() {
}
#+END_SRC
Link to [[test_fun]]
#+NAME: another_test_fun
#+BEGIN_SRC js
function another_test_fun() {
}
#+END_SRC
Link to [[another_test_fun]]
-
Hello Nicolas,
Custom IDs seem to be a good alternative here, although I would think
about the <> part as an invisible part, since I don't expect
it to be visible for e.g. export.
Thanks.
Regards,
timor
You can use sqsh to connect MS-sql too, more info you can see:
https://github.com/tumashu/sql-mssql
At 2016-06-16 14:04:26, "Xi Shen" wrote:
Hi Nicolas,
Please take a look at the updated patch. Changes:
- add ORG-NEWS entry
- add function declaration
- add input file template for `mssql'
23 matches
Mail list logo
