Ok, if I understand you correctly, implementing the mechanism akin to
the latex one, setting a new variable `org-html-prefer-user-labels` would
change the relevant exported HTML for the following piece of org:
--
#+NAME: test_fun
#+BEGIN_SRC js :exports code
function test_fun()
Dear all,
whenever I have python source in an org a file, I get this warning:
Warning (emacs): Python shell prompts cannot be detected.
If your emacs session hangs when starting python shells
recover with `keyboard-quit' and then try fixing the
interactive flag for your interpreter by adjusting
Is it possible to have everything that normally appears in the
[Fundamental] buffer/tab in 'tabbar-ruler' show in the [Common]
buffer/tab please? If so, how?
Thanks
Sharon.
--
A taste of linux = http://www.sharons.org.uk
TGmeds = http://www.tgmeds.org.uk
Debian 8.4, fluxbox 1.3.7, emacs 25.0.95
Thanks Nicolas! I will consider to sign FSF the next time :)
On Fri, Jun 17, 2016 at 6:29 AM Nicolas Goaziou
wrote:
> 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
Hello,
"Charles C. Berry" writes:
> In looking over ob-lob.el, I noticed that the `org-babel-library-of-babel'
> docstring is misleading:
>
> #+BEGIN_QUOTE
> Library of source-code blocks.
> This is an association list. Populate the library by adding
> files to `org-babel-lob-files'.
> #+END_Q
Hello,
timor writes:
> Ok, if I understand you correctly, implementing the mechanism akin to
> the latex one, setting a new variable `org-html-prefer-user-labels` would
> change the relevant exported HTML for the following piece of org:
>
> --
> #+NAME: test_fun
> #+BEGIN_SRC
Hello Nicolas,
2016-06-20 14:52 GMT+02:00 Nicolas Goaziou :
> They have no influence over the link description (which is "1" in both
> cases, as you noticed). If you want to change the description, simply
> provide one:
>
> [[test_fun][whatever]]
Sorry for not being able to express myself more
Hi,
I am working as a sysadmin, In the organization, we use 2 tools to keep
track of requests sent by the customers/users. As you can expect, those
tools are not meant to be used to track all the gritty details of a
sysadmin's job.
So I am turning to org-mode (that I used for years) and its commu
Roland Everaert writes:
> Hi,
>
> I am working as a sysadmin, In the organization, we use 2 tools to
> keep track of requests sent by the customers/users. As you can expect,
> those tools are not meant to be used to track all the gritty details
> of a sysadmin's job.
>
> So I am turning to org-mo
Hello,
After moving ob-shell.el over to lexical binding (2108f0c), emacs -Q
with "(require 'ob-shell)" reports
Debugger entered--Lisp error: (wrong-type-argument sequencep function)
concat("org-babel-execute:" function)
(intern (concat "org-babel-execute:" name))
[...]
It see
On Mon, Jun 20, 2016 at 9:10 AM, Eric Abrahamsen
wrote:
> Roland Everaert writes:
>
>> Hi,
>>
>> I am working as a sysadmin, In the organization, we use 2 tools to
>> keep track of requests sent by the customers/users. As you can expect,
>> those tools are not meant to be used to track all the gr
Hi,
On 06/20/2016 11:56 AM, Kyle Meyer wrote:
Hello,
After moving ob-shell.el over to lexical binding (2108f0c), emacs -Q
with "(require 'ob-shell)" reports
Debugger entered--Lisp error: (wrong-type-argument sequencep function)
concat("org-babel-execute:" function)
(intern
Charles Millar writes:
> Hi,
>
>
> On 06/20/2016 11:56 AM, Kyle Meyer wrote:
>> Hello,
>>
>> After moving ob-shell.el over to lexical binding (2108f0c), emacs -Q
>> with "(require 'ob-shell)" reports
>>
>> Debugger entered--Lisp error: (wrong-type-argument sequencep function)
>>conca
Hello,
Kyle Meyer writes:
> Yep, org-babel-load-languages will end up processing (shell . t) to
> (require 'ob-shell), so this is the same underlying issue.
I actually broke ob-shell when switching to lexical-binding a few hours
ago. I just "unbroke" it.
Regards,
--
Nicolas Goaziou
timor writes:
> The thing is, I have a lot of code blocks that define functions, which
> are named exactly after that function. And as I frequently want to
> reference one of those in the text, I don't want to say
>
> [[test_fun][test_fun]] ..
> [[another_long_function][another_long_function
When I evaluate the following the above error results (this source blosk
and all others that are similar evaluated successfully a few days ago)
#+NAME: SCHEDAP
#+begin_src rec :data foo.rec :type Finance :fields
AccountDate,Description,AccountAmount :results silent
(File = 'RevTrust' && Acco
When org-export-with-tags is set to t, tags on headlines are
exported. Is there a similar way to export FILETAGS as well?
Thanks,
Arun Isaac.
signature.asc
Description: PGP signature
Hi,
I got below error after I called (org-notify-start). It seems the
dbus-error happens very close to the task notification. I wonder if
org-notify uses dbus.
Error: (dbus-error "No connection to bus" :session)
Warning: notification for "Go to dental in 30 mins." behind schedule!
Error: (dbus-er
18 matches
Mail list logo