Re: [O] Bleeding edge in elpa

Richard Y. Kim writes: > # server.mk has the elpaplus makefile target > echo " include mk/server.mk" >> Makefile […] > # Undo the change made above > git checkout Makefile You know, local.mk was introduced specifically so you wouldn't have to do anything like that. Regards, Achim. -- +<[Q+ Matr

Re: [O] Citation syntax: a revised proposal

Hello all, I’ve pushed an update to my branch. The major change is to use citeproc-java for the generation of the bibliography and the parsing of names. The former is straightforward. For the latter, I have created a CSL file which outputs author-year citations in an easy-to-parse format. These

Re: [O] [PATCH] Re: autoloads not working correctly for org-table.el?

Eric Abrahamsen writes: > Eric Abrahamsen writes: > >> Eric S Fraga writes: >> >>> On Wednesday, 4 Mar 2015 at 17:28, Eric Abrahamsen wrote: >>> >>> [...] >>> I'm still seeing an issue where, if I start right off typing a big paragraph of text at the top of the message (no salutation

[O] [PATCH] Re: autoloads not working correctly for org-table.el?

Eric Abrahamsen writes: > Eric S Fraga writes: > >> On Wednesday, 4 Mar 2015 at 17:28, Eric Abrahamsen wrote: >> >> [...] >> >>> I'm still seeing an issue where, if I start right off typing a big >>> paragraph of text at the top of the message (no salutation or anything), >>> all the lines *aft

Re: [O] Multiple (identical) RESULTS blocks of one code block?

Hi Rainer, 2015ko martxoak 9an, Rainer M Krug-ek idatzi zuen: > > Hi > > Consider the following: > > --8<---cut here---start->8--- > * The calculation > #+NAME: testcode :exports both It looks like you’ve tried to put a header argument into the name. Is it mer

Re: [O] Bleeding edge in elpa

tftor...@tftorrey.com (T.F. Torrey) writes: > I wonder how much effort it would take to copy onto my own machine the > scripts on the server that package the git maint version into an ELPA > version, and modify them to package master instead. Probably not much. The shell script below is what I u

Re: [O] Bleeding edge in elpa

Hi Terry, 2015ko martxoak 9an, "T.F. Torrey"-ek idatzi zuen: > > Hello, > > Rasmus writes: > >> As I think somebody said, the correct "fix" to this problem is more >> frequent released. I'm sure Bastien would appreciate help with this. >> Do you want to volunteer? > > If the goal is to have the

Re: [O] Citation syntax: Underscore MUST(?) be allowed in cite keys?

Hi Eric and all, Eric S Fraga writes: > On Monday, 9 Mar 2015 at 09:05, Richard Lawrence wrote: > >> Another option would be to allow clause-ending punctuation in all keys, >> but introduce some kind of optional syntax to express `this key ends > > No, please no! I would say that the majority

Re: [O] Citation syntax: Underscore MUST(?) be allowed in cite keys?

Richard Lawrence writes: > Oh dear, you're right. Where do that initial comma and space come from? > I guess BibLaTeX inserts them automatically? Does that happen in all > styles? The default value is determined by \postnotedelim. So assuming spaces not stripped \renewcommand{\postnotedelim}{

Re: [O] [PATCH] Adding a BEAMER_HEADER_EXTRA tag, allows short titles, etc.

Hi Matthew, Matthew Gidden writes: Thanks for the patch. > I ran into the issue that many others have cited: an inability to add short > titles, etc., to org-mode-generated Beamer presentations [1, 2, 3]. This > patch allows such capability through a BEAMER_HEADER_EXTRA tag, which is > placed a

Re: [O] [PATCH] Adding a BEAMER_HEADER_EXTRA tag, allows short titles, etc.

HI Nic, On Mon, Mar 9, 2015 at 6:19 PM, Nicolas Goaziou wrote: > Hello, > > Matthew Gidden writes: > > > I ran into the issue that many others have cited: an inability to add > short > > titles, etc. to org-mode-generated Beamer presentations [1, 2, 3]. This > > patch allows such capability t

Re: [O] Internal Links with Spaces

I think you need to set (setq org-id-link-to-org-use-id 'create-if-interactive) Then the usual C-c l and C-c C-l should work to store links and insert them. It might be worth noting though, that in my experience, this is most useful for links within a file, or to files in your agenda list. org d

Re: [O] [PATCH] Adding a BEAMER_HEADER_EXTRA tag, allows short titles, etc.

Hello, Matthew Gidden writes: > I ran into the issue that many others have cited: an inability to add short > titles, etc. to org-mode-generated Beamer presentations [1, 2, 3]. This > patch allows such capability through a BEAMER_HEADER_EXTRA tag, which is > placed after title, author, etc., but

Re: [O] Citation syntax: Underscore MUST(?) be allowed in cite keys?

Rasmus writes: > Richard Lawrence writes: > >> Suppose you often write citations like: >> >> [cite: See @Doe99, and references therein, for more.] >> >> [...] and rendered like: >> >> See Doe (1999), and references therein, for more. > > This is slightly OT, but it comes up frequently eno

[O] [PATCH] Adding a BEAMER_HEADER_EXTRA tag, allows short titles, etc.

Hi folks, I ran into the issue that many others have cited: an inability to add short titles, etc., to org-mode-generated Beamer presentations [1, 2, 3]. This patch allows such capability through a BEAMER_HEADER_EXTRA tag, which is placed after title, author, etc., but before `\begin{document}`.

Re: [O] Citation syntax: Underscore MUST(?) be allowed in cite keys?

Richard Lawrence writes: > Suppose you often write citations like: > > [cite: See @Doe99, and references therein, for more.] > > [...] and rendered like: > > See Doe (1999), and references therein, for more. This is slightly OT, but it comes up frequently enough that it's worth pointing ou

Re: [O] Internal Links with Spaces

On Mon, Mar 9, 2015 at 10:38 AM, Leo Ufimtsev wrote: > On the side, if of any help: > > I generally use ID's for linking to headings. > The benefit is that headings can be re-named safley and links still work. A great suggestion. I wasn't aware of the feature, and renaming safety is a great benef

Re: [O] [bug?] org-repair-property-drawers does not repair whole file

Hi Nicolas, org-mode developers and users, * Nicolas Goaziou [09. Mar. 2015]: > Gregor Zattler writes: > I see invalid property drawers, e.g., > > > :PROPERTIES: > > :Xxxx: Xxx, xx Xxx xx:xx:xx + > > :Xxxx: Xxx Xx > > :Xxx-XX: > > :Xxx: XXX XXX - XX xx xx.xx.

Re: [O] Citation syntax: Underscore MUST(?) be allowed in cite keys?

On Monday, 9 Mar 2015 at 08:44, Thomas S. Dye wrote: [...] > No, you have it right and clearly have a use for shortcuts. If you want > to type shortcut citations yourself, then the choice is either to accept > some kind of terminator, e.g. {}, or a restriction that citation keys > not end in pu

Re: [O] Bleeding edge in elpa

Achim Gratz writes: > The version of package manager that people most likely use today always > choses the latest version from _any_ archive available when you update. > You can't tell it to consider some archive more authoritative than > another or that it should stick with whatever source archi

Re: [O] Citation syntax: Underscore MUST(?) be allowed in cite keys?

Hi Tom and all, "Thomas S. Dye" writes: > The problem is limited to the shortcut citations and doesn't affect the > [cite: ...] form, which can be expected to work without modification > wherever it is placed IIUC. Actually, it occurs to me now that this might even affect the [cite: ...] form,

Re: [O] Citation syntax: Underscore MUST(?) be allowed in cite keys?

Eric S Fraga writes: > On Monday, 9 Mar 2015 at 07:49, Thomas S. Dye wrote: > > [...] > >> Do you have a use for the shortcuts? I doubt I'd use them. > > Wouldn't the shortcut be the most attractive to use generally unless you > have need for the extra capability of the full [cite:] syntax? > >

Re: [O] Bleeding edge in elpa

T.F. Torrey writes: > The package manager can only handle one version of a package *per > archive*, so instead use one archive per version. The version of package manager that people most likely use today always choses the latest version from _any_ archive available when you update. You can't tell

Re: [O] Citation syntax: Underscore MUST(?) be allowed in cite keys?

On Monday, 9 Mar 2015 at 07:49, Thomas S. Dye wrote: [...] > Do you have a use for the shortcuts? I doubt I'd use them. Wouldn't the shortcut be the most attractive to use generally unless you have need for the extra capability of the full [cite:] syntax? The vast majority of my citations, e.

Re: [O] Citation syntax: Underscore MUST(?) be allowed in cite keys?

Aloha Eric, Eric S Fraga writes: > On Monday, 9 Mar 2015 at 09:05, Richard Lawrence wrote: > > [...] > >> Another option would be to allow clause-ending punctuation in all keys, >> but introduce some kind of optional syntax to express `this key ends > > No, please no! I would say that the majo

Re: [O] Citation syntax: Underscore MUST(?) be allowed in cite keys?

On Monday, 9 Mar 2015 at 09:05, Richard Lawrence wrote: [...] > Another option would be to allow clause-ending punctuation in all keys, > but introduce some kind of optional syntax to express `this key ends No, please no! I would say that the majority of my citations are at the end of sentence

Re: [O] [bug?] org-repair-property-drawers does not repair whole file

Gregor Zattler writes: > No. I removed the line numbers so that the stars of the headings > are at the first column and invoced `org-repair-property-drawers' > in the same way as described above. The buffer remains > unmodified and the output is `nil'. I cannot reproduce it. >> Is it possible

Re: [O] Citation syntax: Underscore MUST(?) be allowed in cite keys?

Richard Lawrence writes: > Hi Tom and all, > > "Thomas S. Dye" writes: > >> Richard Lawrence writes: >> >>> But my opinion probably shouldn't count for much on this >>> point, because I don't use a citation manager myself (I use org-bibtex), >>> and I write my own keys. >> >> Oh my. This is a

Re: [O] Multiple (identical) RESULTS blocks of one code block?

Hello, Rainer M Krug writes: > Consider the following: > > * The calculation > #+NAME: testcode :exports both > #+begin_src R :session test > runif(10) > #+end_src > > > * summary of the results > First time > #+RESULTS: testcode :exports both > | 0.772744940361008 | > | 0.170518629485741 | >

Re: [O] Bleeding edge in elpa

Hello, Sebastien Vauban writes: >> As Grant pointed out, it’s a lot more convenient working inside Emacs >> for switching between versions and such. > > How do you switch between versions in ELPA? IIUC, you only get the > latest version, and if that one is not right, you're kind of stuck: you >

Re: [O] Citation syntax: Underscore MUST(?) be allowed in cite keys?

Hi Tom and all, "Thomas S. Dye" writes: > Richard Lawrence writes: > >> But my opinion probably shouldn't count for much on this >> point, because I don't use a citation manager myself (I use org-bibtex), >> and I write my own keys. > > Oh my. This is a lot to keep in your head as a bibliogra

Re: [O] Beamer Hello World Help Request

On Sunday, 8 Mar 2015 at 10:47, Matthew Gidden wrote: > FWIW, I was a complete noob and was exporting to a Latex PDF (C-c C-e l p) > instead of a Beamer PDF (C-c C-e l P). Sorry for spamming the list! No worries! I still do this every now and again... :( Glad you figured it out. -- : Eric S Fr

Re: [O] Internal Links with Spaces

On the side, if of any help: I generally use ID's for linking to headings. The benefit is that headings can be re-named safley and links still work. There is an org-module called 'org-id', which when enabled in conjunction with the variable below allows you to automatically generate a unique

Re: [O] Multiple (identical) RESULTS blocks of one code block?

John Kitchin wrote: > Rainer M Krug writes: >> >> Consider the following: >> >> * The calculation >> #+NAME: testcode :exports both >> #+begin_src R :session test >> runif(10) >> #+end_src >> >> >> * summary of the results >> First time >> #+RESULTS: testcode :exports both >> | 0.772744940361008

[O] Internal Links with Spaces

Hi List, I'd like to re-raise the issue discussed here . In short, storing and inserting an internal link to a headline containing spaces using org-store-link and org-insert-link causes export to fail because the space is "hexified" into %20. I

Re: [O] Multiple (identical) RESULTS blocks of one code block?

I don't believe this is possible out of the box. The first RESULTS block from the beginning of the buffer will be updated, and not the others. You might be able to use a hook function to do this, something like: #+BEGIN_SRC emacs-lisp (defun update-results () (interactive) ;; get name of src bl

Re: [O] Citation syntax: Underscore MUST(?) be allowed in cite keys?

Vaidheeswaran C writes: > By saying "bibtex is not a requirement", I said "exporting to bibtex". You talked about Zotero but showed a bibtex entry. Therefore exporting from Zotero to bibtex may not be a requirement, there may be a direct interface to Zotero, eventually. We are at the start of t

Re: [O] [bug?] org-repair-property-drawers does not repair whole file

Hi Nicolas, * Nicolas Goaziou [08. Mar. 2015]: > Gregor Zattler writes: > >> Sadly no: I reapplied `org-repair-property-drawers' on my org >> file with no customisation at all: >> >> emacs-snapshot -Q -nw -L /home/grfz/src/org-mode/lisp/ file.org >> ~/src/org-mode/etc/ORG-NEWS >> >> I loaded `o

Re: [O] Citation syntax: Underscore MUST(?) be allowed in cite keys?

Vaidheeswaran C writes: > Believe me, if I had quick access to pandoc-hs, there would be a > ox-pandoc-citeproc already in the tree by now. My opinion would be to perhaps not put too much energy into anything Haskell. It's extremely annoying when you don't have the luxury of prebuild packages.

Re: [O] Citation syntax: a revised proposal

On Monday 09 March 2015 04:10 PM, Sebastien Vauban wrote: > What is <<<...>>>? (info "(org) Radio targets")

Re: [O] Citation syntax: Underscore MUST(?) be allowed in cite keys?

On Monday 09 March 2015 03:19 PM, Stefan Nobis wrote: > Vaidheeswaran C writes: > >> On Monday 09 March 2015 02:27 PM, Stefan Nobis wrote: > >>> IMHO keys with lots of ??? in them are a sign of a data problem. >>> Therefore the author should solve the root cause. > >> Not in the specific case t

Re: [O] Babel: RESULTS for no value

Greetings Charles. "Charles C. Berry" writes: >> To achieve this behaviour, I have set >> >> (defvar org-babel-default-header-args:processing >> '((:results . "html") (:exports . "results")) >> "Default arguments when evaluating a Processing source block.") > > I think you can replace > > : (

Re: [O] Citation syntax: a revised proposal

Hello Nicolas, Nicolas Goaziou wrote: > Honestly, Org is already full of cryptic symbols, e.g., {{{...}}} > @@...@@, <<<>>>, <<...>>, and so on. This is not worse than the > rest of Org. What is <<<...>>>? PS- Not easy to search for that in the Org manual in Emacs: neither << nor <<< are

[O] Multiple (identical) RESULTS blocks of one code block?

Hi Consider the following: --8<---cut here---start->8--- * The calculation #+NAME: testcode :exports both #+begin_src R :session test runif(10) #+end_src * summary of the results First time #+RESULTS: testcode :exports both | 0.772744940361008 | | 0.170518

Re: [O] Citation syntax: Underscore MUST(?) be allowed in cite keys?

Vaidheeswaran C writes: > On Monday 09 March 2015 02:27 PM, Stefan Nobis wrote: >> IMHO keys with lots of ??? in them are a sign of a data problem. >> Therefore the author should solve the root cause. > Not in the specific case that I cited. The Bib entry is a pointer to > a website. I would s

Re: [O] Citation syntax: Underscore MUST(?) be allowed in cite keys?

On Monday 09 March 2015 02:27 PM, Stefan Nobis wrote: > IMHO keys with lots of ??? in them are a sign of a data problem. > Therefore the author should solve the root cause. @misc{center_for_history_and_new_media_zotero_, title = {Zotero {Quick} {Start} {Guide}}, url = {http://

Re: [O] Bleeding edge in elpa

Nikolai Weibull wrote: > On Sat, Mar 7, 2015 at 3:47 PM, Xavier Maillard wrote: >> Nikolai Weibull writes: > >>> Would it be of interest to anyone else if the bleeding edge version >>> was available via elpa? > >> Isn't it already available via M-x package interface ? > > No, only the version bas

Re: [O] Citation syntax: Underscore MUST(?) be allowed in cite keys?

t...@tsdye.com (Thomas S. Dye) writes: > It strikes me that basing core features of the citation syntax on > the software users happen to be using today is a bit like this--at > some point the design of the system will prove unprepared for new > developments. I don't think this is a big problem.

Re: [O] Bleeding edge in elpa

Hello, Achim Gratz writes: > It doesn't get any easier than it already is. Having both a stable and > an unstable version of Org avilable via ELPA is a non-starter for the > simple reason that the package manager can't deal with the versioning > problems this would introduce. I think this is n

Re: [O] Bleeding edge in elpa

Hello again, Rasmus writes: >> I want to collaborate on Org files with my wife and parents, > ^^^ > > Do you? It sounds cool! It's complicated. I've convinced my parents to begin writing memoir-type books, and my wife works in non-profit, where good books are always good solution

Re: [O] Bleeding edge in elpa

Hello again, Achim Gratz writes: > Rasmus writes: >> I agree. I have the same problem when I build documents (via CI) on a >> remote Debian server where I don't want to mess around with anything more >> than what comes with Emacs by default. > > You can use a tarball and the support for manual

Re: [O] Bleeding edge in elpa

Hello, Rasmus writes: > As I think somebody said, the correct "fix" to this problem is more > frequent released. I'm sure Bastien would appreciate help with this. > Do you want to volunteer? If the goal is to have the latest and greatest version of Org available via ELPA (for all the reasons s

Re: [O] Zotero csl file that uses parenthetical style for citations

On Monday 09 March 2015 12:04 PM, Thomas S. Dye wrote: > I'm happy to have you here and look forward to your contributions to Org > mode. I hope you enjoy the community as much as I do. I think Org mode > rocks. Thanks a lot.