Re: [O] Any existing function to copy the src block to clipboard

[Josiah Schwab]

Hello Giri,

> Is there a easy way to copy the entire contents of the current src block
> cursor is located to clipboard ?

There is org-babel-mark-block, which is bound to C-c C-v C-M-h.  This
will select the current src block and then you can copy as usual.

Hope that helps,
Josiah

[O] Any existing function to copy the src block to clipboard

[Giri Prashanth]

Hi,

Is there a easy way to copy the entire contents of the current src block
cursor is located to clipboard ?

Thank you for your responses in advance.

-GP

Re: [O] Bug: incorrect export for LaTeX [8.2.10 (release_8.2.10 @ c:/emacs25-91/share/emacs/25.0.91/lisp/org/)]

[Rasmus]

Nicolas Goaziou  writes:

> Hello,
>
> 9661031 <9661...@gmail.com> writes:
>
>> When you use a headline which is more than 7th level,the exported LaTeX file
>> raises an error in typesetting. Here is an example (org file):
>>
>> ===
>> * one
>> ** two
>> *** three
>>  four
>> * five
>> ** six
>> *** seven
>>  eight
>> ===
>>
>> This happens because nesting of enumerate environment in LaTeX is limited.
>> I think the program should export an LaTeX file that successfully makes
>> a PDF file even though the solution is dirty.
>
> Fair enough. Do you have a proposal for deeply nested headlines (or
> items)?

Use this header:

#+options: h:0
#+latex_header: \usepackage{enumitem}
#+latex_header: \setlistdepth{9}
#+latex_header: \setlist[enumerate]{label=(\arabic*)}


I don’t think we need to do anything.  If we wanted to support this we’d
probably need to load enumerate (which is not a bad package...).  We have
worse offenders of manual config.  Local TOCs spring to mind.
http://orgmode.org/org.html#fn-113

Rasmus

-- 
I almost cut my hair, it happened just the other day

Re: [O] How to prevent loading of org-agenda-files?

[Eric S Fraga]

On Wednesday,  2 Mar 2016 at 14:22, John Kitchin wrote:
> I guess the OP opens a new emacs instance, which might be loading agenda
> files each time on initialization?

Indeed, but why load the agenda on initialisation then if that's not
what is wanted always...?

> If that is the case, emacsclient is probably the solution. or Open files in
> a new frame.

Yes, possible solution.
-- 
: Eric S Fraga (0xFFFCF67D), Emacs 25.0.91.1, Org release_8.3.4-626-gb62d55

Re: [O] How to prevent loading of org-agenda-files?

[John Kitchin]

I guess the OP opens a new emacs instance, which might be loading agenda
files each time on initialization?

If that is the case, emacsclient is probably the solution. or Open files in
a new frame.

John

---
Professor John Kitchin
Doherty Hall A207F
Department of Chemical Engineering
Carnegie Mellon University
Pittsburgh, PA 15213
412-268-7803
@johnkitchin
http://kitchingroup.cheme.cmu.edu


On Wed, Mar 2, 2016 at 1:41 PM, Eric S Fraga  wrote:

> On Thursday,  3 Mar 2016 at 01:46, Louis Turk wrote:
> > Hi everyone,
> >
> > I use emacs all day long for many purposes, including programming. I
> > open emacs with org-mode on one desktop, and leave it running
> > continually. I do not want emacs to load the org-agenda files every time
> > I open a source-code file, but rather only when I open a file with the
> > .org extension. How can this be done?
>
> Why would your agenda files get loaded whether you visit an org file or
> any other file?  You must have customised something that opens those
> files as the default behaviour is to open them only if you invoke one of
> the agenda commands.
> --
> : Eric S Fraga (0xFFFCF67D), Emacs 25.0.91.1, Org release_8.3.4-626-gb62d55
>
>

Re: [O] Add caching to org-buffer-property-keys

[Thierry Banel]

Nice function!
Maybe a rewrite of (org-read-property-name) calling
(org-entry-properties) could speed up things.
(org-entry-properties) returns an assoc list of the local header properties.

Le 02/03/2016 12:29, Karl Voit a écrit :
> Hi!
>
> In short: can we get a cached org-buffer-property-keys please?
>
>
> My background story:
>
> I love using following function which gives me a neat functionality:
> I mark a string, press the keybinding shortcut, and gets asked which
> property should be replaced/filled with the marked region text.
>
> Very handy when you've got a new phone number of a contact which
> should find its way to the associated property.
>
> (defun my-org-region-to-property ( property)
>   (interactive)
>   ;; if no region is defined, do nothing
>   (if (use-region-p)
>   ;; if a region string is found, ask for a property and set property to
>   ;; the string in the region
>   (let ((val (replace-regexp-in-string
>   "\\`[ \t\n]*" ""
>   (replace-regexp-in-string "[ \t\n]*\\'" ""
> (substring (buffer-string)
>(- (region-beginning) 
> 1)
>(region-end
>  )
> ;; if none was stated by user, read property from user
> (prop (or property
>   (org-read-property-name
> ;; set property
> (org-set-property prop val
>
> A big drawback is that I have to wait 18 seconds(!) until
> org-read-property-name which calls org-buffer-property-keys asks for
> the property. This is a real show stopper for this cool function.
>
> Since the properties of a buffer do not change that often, caching
> its previous result would make sense to me. This way, I only have to
> wait 18 seconds once per file on the first call.
>
> An alternative would be a org-read-property-name which uses only the
> properties of the current heading.
>
>
> Thanks for your support!
>

[O] How to prevent loading of org-agenda-files?

[Louis Turk]

Hi everyone,

I use emacs all day long for many purposes, including programming. I
open emacs with org-mode on one desktop, and leave it running
continually. I do not want emacs to load the org-agenda files every time
I open a source-code file, but rather only when I open a file with the
.org extension. How can this be done?

Lou

Re: [O] How to omit "_" in org?

[Nick Dokos]

童俊翔  writes:

> I want to write CN01_003_pla, in which the “_” doesn’t represent subscript. 
> How to do this?
>
> Thank you!

#+OPTIONS: ^:nil

or

#+OPTIONS: ^:{}

The second gives you the ability to have super/subscripts
by enclosing them in braces, so

a_b gives an underscore while a_{b} gives a subscript.

--
Nick

Re: [O] ox-beamer.el tableofcontents, a suggestion

[Joseph Vidal-Rosset]

Dear Eric,

Many thanks for this more elegant solution that I had just tested, and it
works!

I add that

#+OPTIONS:  toc:nil

is necessary to avoid a repetition of table of contents.

Thanks again !

Jo.




2016-03-02 14:42 GMT+01:00 Eric S Fraga :

> On Wednesday,  2 Mar 2016 at 14:29, Joseph Vidal-Rosset wrote:
> > Of course it would be better to add this function as new option and to
> > avoid this change of code. I do not know how to do.
>
> I find it reasonably straightforward to simply add the following line to
> my beamer org files:
>
> #+latex_header:
> \AtBeginSection[]{\begin{frame}\frametitle{Topic}\tableofcontents[currentsection,hideothersubsections]\end{frame}}
>
> so no need to play with the elisp code...
>
> --
> : Eric S Fraga (0xFFFCF67D), Emacs 25.0.91.1, Org release_8.3.3-456-g164555
>

[O] How to omit "_" in org?

[童俊翔]

I want to write CN01_003_pla, in which the “_” doesn’t represent subscript. How 
to do this?

Thank you!

Re: [O] org-collector - propview display problems

[dche]

This function interested me in order to produce subset of data in tabular 
with search criteria included in properties field. I hoped to
use this kind of approach as a kind of database and possibly use one of 
property field to include an information about a link to a file or the use 
of attachment (if possible this way).

This function is in contrib folder. Is this status that makes it not 
supported ?

Regards

Re: [O] ox-beamer.el tableofcontents, a suggestion

[Eric S Fraga]

On Wednesday,  2 Mar 2016 at 14:29, Joseph Vidal-Rosset wrote:
> Of course it would be better to add this function as new option and to
> avoid this change of code. I do not know how to do.

I find it reasonably straightforward to simply add the following line to
my beamer org files:

#+latex_header: 
\AtBeginSection[]{\begin{frame}\frametitle{Topic}\tableofcontents[currentsection,hideothersubsections]\end{frame}}

so no need to play with the elisp code...

-- 
: Eric S Fraga (0xFFFCF67D), Emacs 25.0.91.1, Org release_8.3.3-456-g164555

[O] ox-beamer.el tableofcontents, a suggestion

[Joseph Vidal-Rosset]

Hello,


With beamer presentation it is often useful to put this latex code just
after \maketitle:

% outline
\AtBeginSection[]
{
 \begin{frame}
  \frametitle{}
  \small
  \tableofcontents[currentsection,hideothersubsections]
  \normalsize
 \end{frame}
}

the interest is reminding the outline to audience after each begin of a new
section.

In org-mode it is possible to export this code if the following lines of
code of ox-beamer.el  :
;
;; 11. Table of contents.
 (let ((depth (plist-get info :with-toc)))
   (when depth
 (concat
  (format "\\begin{frame}%s{%s}\n"
  (org-beamer--normalize-argument
   org-beamer-outline-frame-options 'option)
  org-beamer-outline-frame-title)
  (when (wholenump depth)
(format "\\setcounter{tocdepth}{%d}\n" depth))
  "\\tableofcontents\n"
  "\\end{frame}\n\n")))
;

are replaced by:

;;;
;; 11. Table of contents.
 (let ((depth (plist-get info :with-toc)))
   (when depth
 (concat
  (format
   "\\AtBeginSection\[\]\{
   \\begin{frame}\n
\\small\n"
  (org-beamer--normalize-argument
   org-beamer-outline-frame-options 'option)
  org-beamer-outline-frame-title)
  (when (wholenump depth)
(format "\\setcounter{tocdepth}{%d}\n" depth))
  "\\tableofcontents\[currentsection,hideothersubsections\]\n"
  "\\normalsize\n"
  "\\end{frame}\n
}\n\n")))
;

it works in my setup.

Of course it would be better to add this function as new option and to
avoid this change of code. I do not know how to do.

At least it could be useful someone else.

Best wishes,

Jo.

[O] Add caching to org-buffer-property-keys

[Karl Voit]

Hi!

In short: can we get a cached org-buffer-property-keys please?


My background story:

I love using following function which gives me a neat functionality:
I mark a string, press the keybinding shortcut, and gets asked which
property should be replaced/filled with the marked region text.

Very handy when you've got a new phone number of a contact which
should find its way to the associated property.

(defun my-org-region-to-property ( property)
  (interactive)
  ;; if no region is defined, do nothing
  (if (use-region-p)
  ;; if a region string is found, ask for a property and set property to
  ;; the string in the region
  (let ((val (replace-regexp-in-string
  "\\`[ \t\n]*" ""
  (replace-regexp-in-string "[ \t\n]*\\'" ""
(substring (buffer-string)
   (- (region-beginning) 1)
   (region-end
 )
;; if none was stated by user, read property from user
(prop (or property
  (org-read-property-name
;; set property
(org-set-property prop val

A big drawback is that I have to wait 18 seconds(!) until
org-read-property-name which calls org-buffer-property-keys asks for
the property. This is a real show stopper for this cool function.

Since the properties of a buffer do not change that often, caching
its previous result would make sense to me. This way, I only have to
wait 18 seconds once per file on the first call.

An alternative would be a org-read-property-name which uses only the
properties of the current heading.


Thanks for your support!

-- 
mail|git|SVN|photos|postings|SMS|phonecalls|RSS|CSV|XML to Org-mode:
   > get Memacs from https://github.com/novoid/Memacs <

https://github.com/novoid/extract_pdf_annotations_to_orgmode + more on github

Re: [O] non-standard link errors

[Simon Thum]

Hi,

after some testing I see my assumption that without export function no 
links are generated was wrong. All fine, and thanks for your 
tirelessness in explaining it so even I get it ;)


Cheers,

Simon

On 03/02/2016 10:28 AM, Nicolas Goaziou wrote:

Hello,

Simon Thum  writes:


this reminds me of my issue with tel: links. I also would have
preferred to have them exported "pass-through", but AFAICT this
requires me to come up with a trival function for every possible
backend: those I know, those I don't, and those that may not exist
yet.

I cannot switch to the raw: solution (due to vcard export). I'm not
currently experiencing problems, but I would like to suggest that
maybe such a trival default handler could be added to the backends as
some well-known property to be available to those who set the broken
link handler to e.g. 'fallback. The onus would be on the user to do
this, since correctness of output may suffer. Of course, basic
sanitation should still be done in such a handler, but preferably no
spectacular failure*.


As I explained, there is already a default handler in every major
back-end.

However, Org needs to tell links with a type from the others (internal
links). This is what `org-add-link-type' is for. This has nothing to do
with export.

To put it differently, when Org encounters a foo:bar link, there are two
options. Either "foo" is a registered link type, or not. If the former,
Org tries to use whatever export function was provided, or fall-backs to
the default handler. In the latter, Org considers it to be an internal
link. Since there is probably no #+NAME: foo:bar, <>
or * foo:bar in the document, the export process returns an error, by
default.


Regards,

[O] Agenda headline in export(er)

[Simon Thum]

Hi all,

this is probably a basic question. I have many small dates specified like

** <2016-03-14 16:00> Do Stuff


In the Agenda View, I see "Do Stuff" well-aligned and nice. However I 
also sync over icalendar to my phone, where the title shows up as


<2016-03-14 16:00> Do Stuff

which fills my calendar overviews with the most redundant information I 
could think of. I looked around but I did not find a clear good way to 
do filter the timestamp. I want it so I only have


"Do Stuff"

in the icalendar title.

Any suggestions?

Thanks in advance,

Simon

Re: [O] non-standard link errors

[Nicolas Goaziou]

Hello,

Simon Thum  writes:

> this reminds me of my issue with tel: links. I also would have
> preferred to have them exported "pass-through", but AFAICT this
> requires me to come up with a trival function for every possible
> backend: those I know, those I don't, and those that may not exist
> yet.
>
> I cannot switch to the raw: solution (due to vcard export). I'm not
> currently experiencing problems, but I would like to suggest that
> maybe such a trival default handler could be added to the backends as
> some well-known property to be available to those who set the broken
> link handler to e.g. 'fallback. The onus would be on the user to do
> this, since correctness of output may suffer. Of course, basic
> sanitation should still be done in such a handler, but preferably no
> spectacular failure*.

As I explained, there is already a default handler in every major
back-end.

However, Org needs to tell links with a type from the others (internal
links). This is what `org-add-link-type' is for. This has nothing to do
with export.

To put it differently, when Org encounters a foo:bar link, there are two
options. Either "foo" is a registered link type, or not. If the former,
Org tries to use whatever export function was provided, or fall-backs to
the default handler. In the latter, Org considers it to be an internal
link. Since there is probably no #+NAME: foo:bar, <>
or * foo:bar in the document, the export process returns an error, by
default.


Regards,

-- 
Nicolas Goaziou

Re: [O] non-standard link errors

[Simon Thum]

Hi,

this reminds me of my issue with tel: links. I also would have preferred 
to have them exported "pass-through", but AFAICT this requires me to 
come up with a trival function for every possible backend: those I know, 
those I don't, and those that may not exist yet.


I cannot switch to the raw: solution (due to vcard export). I'm not 
currently experiencing problems, but I would like to suggest that maybe 
such a trival default handler could be added to the backends as some 
well-known property to be available to those who set the broken link 
handler to e.g. 'fallback. The onus would be on the user to do this, 
since correctness of output may suffer. Of course, basic sanitation 
should still be done in such a handler, but preferably no spectacular 
failure*.


Cheers,

Simon

(*) Because I sync using org exporter, I tend to suffer from those. And 
yes, I'd rather have wrong output I can diagnose than nothing.


On 02/29/2016 07:10 PM, Nicolas Goaziou wrote:

Hello,

Skip Collins  writes:


I have come up with a better solution than globally passing "broken"
links. I defined a new "raw" link type. So now if I want to put a
non-standard link in my export, I can do something like:
Here is a [[raw:foo:/\bar, baz][bad link]].
which is exported in html as:
Here is a bad link.

Now I can have non-standard links included in the output without
disabling link checking for all standard link types. This is how it is
defined in my .emacs:
(org-add-link-type "raw" 'org-raw-follow 'org-raw-export)
(defun org-raw-follow (path))
(defun org-raw-export (path desc format)
   "Export a raw link.
See `org-add-link-type' for details about PATH, DESC and FORMAT."
   (cond
((eq format 'html) (format "%s" path desc))
((eq format 'latex) (format "\\href{%s}{%s}" path desc))
((eq format 'ascii) (format "%s (%s)" desc path))
(t path)))

Perhaps this could be included in the standard Org distribution as a
fallback option for exporting non-standard link types. Emacs/Org does
nothing with the link. The user is responsible for ensuring the output
is correct.


This is already the default behavior for custom types. You don't even
need to use `org-raw-export' or `org-raw-open'. All is needed, is

  (org-add-link-type "raw")

Org requires it so it can tell if the link is an internal link or not.
However, I don't think we need to introduce a particular link type for
that. Users can define whatever they want.


Regards,