Re: [O] [SOLVED] org-20181210 seems to break Column View
Thanks anyway. My bad, it was due to poly-org package which I had installed recently. It broke undo in org buffers too. signature.asc Description: PGP signature
Re: [O] FW: [RFC] Link-type for attachments, more attach options
> No, it's not there. I know of the custom agendas and use it currently. But I
> cannot anywhere specify more than one org-agenda-files parameter, for
> example.
I just tried:
#+begin_src emacs-lisp
(setq org-agenda-custom-commands
(quote (("v" "Test" tags-todo nil
((org-agenda-files '("~/Org/inbox.org"
("w" "Test 2" tags-todo nil
((org-agenda-files
'("~/Knowledge_base/2016/Private/Get_started_with_org_mode/get_started_org_mode.org")))
#+end_src
It works fine for me.
> No, that's not what I want. What I'm talking about is extending org-mode
> conceptually with the concept of 0-level headlines, where the body of that
> "headline" would be everything before the first headline in a file, and where
> I could specify (for example) an attachment-directory and be able to use it
> with this new syntax to link to attached files. I guess I took it a bit far
> with the example of visualizing multiple files from a folder as separate
> headlines inside a single emacs-buffer though. It would be cool to be able to
> do that but my intention was more about introducing the 0-level headline
> concept.
Yeah. But someone needs to volunteer with the patch.
It would be even better if these 0-level headings can be edited from the
referencing file.
Regards,
Ihor
Gustav Wikström writes:
> Hi,
>
>> -Original Message-
>> From: Ihor Radchenko
>> Sent: den 20 november 2018 15:01
>> To: Gustav Wikström
>> Cc: emacs-orgmode
>> Subject: RE: [O] FW: [RFC] Link-type for attachments, more attach options
>>
>> Hi,
>>
>> >Generalize org-agenda by allowing us to have multiple ones, and make
>> them more general by thinking of them as a set of views that works on sets
>> of files. Maybe this is not for all, but I would appreciate to create
>> multiple "agendas" (even though I'd call them "libraries" in instead), and
>> possibly also an aggregate agenda consisting of other agendas.
>>
>> Isn't this already in org? You can use custom agendas with multiple
>> "agendas" (custom commands) and set the files they operate on with org-
>> agenda-files within custom commands.
>
> No, it's not there. I know of the custom agendas and use it currently. But I
> cannot anywhere specify more than one org-agenda-files parameter, for
> example.
>
>>
>> >If two org-mode files exist in the same folder with different names, it
>> would be awesome to think of (and work with) them as two top-level headings
>> inside one org-mode buffer. Similar to two level-1 headings inside an org-
>> mode file. For this to work all properties we can define for regular
>> headings should be possible to define for these "level-0 headings". For
>> example an attachment-folder or ID, a deadline, scheduled date, or TODO-
>> keyword should in that case be configurable on the whole file. I guess some
>> new conventions regarding syntax and existing properties would have to be
>> created as well.
>>
>> You can do something like below. It is pretty much what you want, except I
>> am not sure how to update the headings from local org files. Current org
>> version does not allow `:results replace` on raw org output.
>>
>> * Main heading
>>
>> #+name: org-files-here
>> #+begin_src bash
>> ls *.org
>> #+end_src
>>
>> #+begin_src emacs-lisp :var files=org-files-here() :var stars=(make-string
>> (car (org-heading-components)) ?*) :results raw replace drawer (let ((files
>> (mapcar #'car files)))
>> (cl-loop for file in files
>> concat (with-current-buffer (find-file-noselect file)
>> (concat (format "* %s\n" (buffer-file-name))
>> (replace-regexp-in-string "^\\*" (concat "*" stars)
>> (buffer-string)) #+end_src
>
> No, that's not what I want. What I'm talking about is extending org-mode
> conceptually with the concept of 0-level headlines, where the body of that
> "headline" would be everything before the first headline in a file, and where
> I could specify (for example) an attachment-directory and be able to use it
> with this new syntax to link to attached files. I guess I took it a bit far
> with the example of visualizing multiple files from a folder as separate
> headlines inside a single emacs-buffer though. It would be cool to be able to
> do that but my intention was more about introducing the 0-level headline
> concept.
>
> Thanks for your idea and suggestion though!
>
>>
>> Best,
>> Ihor
>
> Kind Regards,
> Gustav
>
signature.asc
Description: PGP signature
Re: [O] problems with org-tempo
> On Dec 13, 2018, at 2:36 PM, Uwe Brauer wrote:
>
>
> Hi
>
> I hoped that org-tempo would be a substitute for the old beloved org
> template system. well
>
>1. It expands
>2. The syntax is not the same for example I want
>
> Key: b
>Keyword:
>bibliographystyle:plain
>bibliography:/home/oub/texmf/bibtex/bib/bibgraf.bib
>
>
> But
>
> Expands to
>
> #+bibliographystyle:plain
> bibliography:/home/oub/texmf/bibtex/bib/bibgraf.bib:
>
> Which is annoying. It should be
>
> bibliographystyle:plain
> bibliography:/home/oub/texmf/bibtex/bib/bibgraf.bib
>
> Any chance to get that behavior. I don't feel like learning a new tool
> for inserting template, since I am very acquainted with the old one.
>
You need `(require 'org-tempo)', then
#+begin_src emacs-lisp
(tempo-define-template "org-display-bib"
'("bibliographystyle:plain" n
"bibliography:/home/oub/texmf/bibtex/bib/bibgraf.bib" p n)
"
Re: [O] Bug: Special property ITEM without stars [9.1.14]
On Thu, Dec 13, 2018 at 6:28 AM Bernt Hansen wrote: > > Allen Li writes: > > > On Wed, Dec 12, 2018 at 10:00 AM Nicolas Goaziou > > wrote: > >> > >> This is not satisfying, actually. If every item has a single asterisk, > >> you miss hierarchy between headlines in the same tree. > > > > I don't know what you mean. Hierarchy is not displayed normally in > > agenda view anyway, I don't know why displaying it in agenda column > > view via the ITEM property is desirable? > > > > I use hierarchy in my custom agenda view everyday. Please do not remove > this feature. Apparently I'm missing something. How are you using hierarchy in an agenda view? Agenda views are flat, e.g.: tasks: TODO [#A] Some task tasks: TODO [#A] Some task tasks: TODO [#A] Some task tasks: TODO Some task tasks: TODO Some task tasks: TODO Some task If I remember correctly, the reason they're flat is that it generally doesn't make sense to show the hierarchy because it won't make any sense. For example, the following: * TODO Project A ** Some project A notes * Project B ** TODO Some task for B would have this hierarchy in an agenda view if we hypothetically displayed it: tasks: * TODO Project A tasks: ** TODO Some task for B which I think is confusing at best (but I can believe is useful for some work flows if you're careful). > > Thanks, > Bernt
Re: [O] the 'new' template system some questions
I believe it's the melpa one that's often used. https://github.com/joaotavora/yasnippet/blob/master/README.mdown https://www.emacswiki.org/emacs/Yasnippet Best, Mehmet On Thu, Dec 13, 2018, 17:18 Uwe Brauer >>> "William" == William Denton writes: > >> On 13 December 2018, Uwe Brauer wrote: >>> And I used both quite a bit, it seems that the new syntax has a begin >>> and end mandatory. So what I can I with this sort of templates? > >> yasnippet? I think that's what a lot of people moved to. > > Ok I googled it: it is not part of org mode. But package-list-package > returns me to > > Yasnippet melpa > > And > > Yanipped-classic > > In gnus. > > Which is the right one? What do people use. >
[O] problems with org-tempo
Hi I hoped that org-tempo would be a substitute for the old beloved org template system. well 1. It expands
Re: [O] the 'new' template system some questions
>>> "William" == William Denton writes: > On 13 December 2018, Uwe Brauer wrote: >> And I used both quite a bit, it seems that the new syntax has a begin >> and end mandatory. So what I can I with this sort of templates? > yasnippet? I think that's what a lot of people moved to. Ok I googled it: it is not part of org mode. But package-list-package returns me to Yasnippet melpa And Yanipped-classic In gnus. Which is the right one? What do people use. smime.p7s Description: S/MIME cryptographic signature
Re: [O] the 'new' template system some questions
>>> "William" == William Denton writes: > On 13 December 2018, Uwe Brauer wrote: >> And I used both quite a bit, it seems that the new syntax has a begin >> and end mandatory. So what I can I with this sort of templates? > yasnippet? I think that's what a lot of people moved to. What is that? Part of org mode? I can't find it. What's about org-tempo? smime.p7s Description: S/MIME cryptographic signature
Re: [O] the 'new' template system some questions
On 13 December 2018, Uwe Brauer wrote: And I used both quite a bit, it seems that the new syntax has a begin and end mandatory. So what I can I with this sort of templates? yasnippet? I think that's what a lot of people moved to. Bill -- William Denton :: Toronto, Canada --- Listening to Art: https://listeningtoart.org/ https://www.miskatonic.org/ --- GHG.EARTH: http://ghg.earth/ Caveat lector. --- STAPLR: http://staplr.org/
[O] the 'new' template system some questions
Hi I finally upgraded my org version and so start to use the new template system. Although I am a fan of not breaking backwards compatibility I can understand why it was necessary in the rewritten template functionality. First of all thanks it is quite nice. However I have to old templates which I don't know how to translate to the new system. 1.
Re: [O] problem with export of #+BEGIN_src latex :results latex replace :exports results :eval t
>>> "Eric" == Eric S Fraga writes: > On Thursday, 13 Dec 2018 at 16:08, Uwe Brauer wrote: > [...] >> BTW I just saw mail from Nick in which he states >> >>> Why don't you use ? It turns a region into a source block. >> >> In which org version. What command is bound to C-c C-, > Not sure when it was introduced but maybe 9 months ago or so. It's > bound to org-insert-structure-template. >> My version seems not to have it. (Master from last July, I think). > Should be there as the binding was done 8 months ago according to the > git log (39837b4b3). Ok, my version is older, so decided to upgrade. First thing I noted my old templates are useless, the syntax has changed. I will ask about that in a different email. The new command is quite nice, though, thanks for providing it. smime.p7s Description: S/MIME cryptographic signature
Re: [O] [PATCH] org-capture: Add a custom to control save target file or not.
On Thu, Dec 13, 2018 at 11:25 AM Nicolas Goaziou wrote: > > > +(unless (org-capture-get :no-save) > > + ;; Save the target file. > > + (save-buffer)) > > The comment does not look terribly useful. I would put the whole > `unless' in a single line. > > Barring that nitpicking of mine, LGTM! > Thanks. I have made the suggested change, and pushed to master, merged into next.
Re: [O] Mean of a column in a remote table
Hello Eric, Eric S Fraga writes: > Umm, I think you want to do the mean of the remote entries so try: > vmean(remote($1,@2..@>)) but I also wonder whether you need to specify > the column as well for remote references? At least, when I have done > this, I have specified both rows and columns, > e.g. vmean(remote(xxx,@<$>..@>$>)). Yes! That was it. Many thanks for your help. Roger
Re: [O] [PATCH] org-capture: Add a custom to control save target file or not.
Hello, Kaushal Modi writes: > I have formatted 2 patches to address this (attached). If they look fine, I > can commit them to master. Thank you. > +(unless (org-capture-get :no-save) > + ;; Save the target file. > + (save-buffer)) The comment does not look terribly useful. I would put the whole `unless' in a single line. Barring that nitpicking of mine, LGTM! Regards, -- Nicolas Goaziou
Re: [O] Mean of a column in a remote table
On Thursday, 13 Dec 2018 at 10:38, Roger Mason wrote: > Hello Eric, > > Eric S Fraga writes: > >> That should have been @>, not @<. > > | Data | a | > |---+| > | mic_2_in_648_cell | #ERROR | > > #+tblfm: $2=remote($1,vmean(@2..@>)) > > and 'Cells in the region copied, use M-x org-table-paste-rectangle to > paste them in a table.' in the Message buffer. Umm, I think you want to do the mean of the remote entries so try: vmean(remote($1,@2..@>)) but I also wonder whether you need to specify the column as well for remote references? At least, when I have done this, I have specified both rows and columns, e.g. vmean(remote(xxx,@<$>..@>$>)). -- Eric S Fraga via Emacs 27.0.50, Org release_9.1.14-1034-gafcb1d
Re: [O] problem with export of #+BEGIN_src latex :results latex replace :exports results :eval t
On Thursday, 13 Dec 2018 at 16:08, Uwe Brauer wrote: [...] > BTW I just saw mail from Nick in which he states > >> Why don't you use ? It turns a region into a source block. > > In which org version. What command is bound to C-c C-, Not sure when it was introduced but maybe 9 months ago or so. It's bound to org-insert-structure-template. > My version seems not to have it. (Master from last July, I think). Should be there as the binding was done 8 months ago according to the git log (39837b4b3). -- Eric S Fraga via Emacs 27.0.50, Org release_9.1.14-1034-gafcb1d
Re: [O] [PATCH] org-capture: Add a custom to control save target file or not.
On Thu, Dec 13, 2018 at 10:24 AM Kaushal Modi wrote: > > I have formatted 2 patches to address this (attached). If they look fine, > I can commit them to master. > I forgot to properly format the commit messages.. locally, I have fixed the commit message of 0002 patch to the below: = Add :no-save keyword for Org capture templates * lisp/org-capture.el (org-capture-finalize): Do not save the target capture file if :no-save keyword is non-nil in the capture template. * doc/org-manual.org (Template elements), lisp/org-capture.el (org-capture-templates): Document :no-save. Ref: https://lists.gnu.org/r/emacs-orgmode/2018-09/msg00325.html =
Re: [O] problem with export of #+BEGIN_src latex :results latex replace :exports results :eval t
>>> "Eric" == Eric S Fraga writes: > On Thursday, 13 Dec 2018 at 11:55, Uwe Brauer wrote: >> That is for babel. That is I have an org file, which contains matlab and >> latex for the documentation. So I want to cite a reference. There is no >> problem with citep if I don't have the latex in a src block. >> >> However as I said the fortification is much nicer if I put latex in a >> src block. > Yes but my point is that the line that has the citep: link is org syntax > and should therefore not be in the LaTeX src block. Keep the equation > in the src block but take that line to past the end of the block. Oops, you are right and I am wrong, thanks. BTW I just saw mail from Nick in which he states > Why don't you use ? It turns a region into a source block. In which org version. What command is bound to C-c C-, My version seems not to have it. (Master from last July, I think). smime.p7s Description: S/MIME cryptographic signature
Re: [O] [PATCH] org-capture: Add a custom to control save target file or not.
On Thu, Dec 13, 2018 at 10:08 AM Kaushal Modi wrote: > Hello Nicolas, > > While we are planning to cut Org 9.2 release this week, this one > regression in the Org Capture and auto-saving behavior comes to my mind, > that I think should be fixed. > > Summary: > > In Org 9.1.x, org-capture target files got auto-saved after C-c C-c when > ending the capture. In Org master branch, that stopped happening. > > As per your last proposal, we should revert > https://code.orgmode.org/bzg/org-mode/commit/b4422add3745c26ec3b2e11b8da425844b2e9d3d > and then add a :no-save option that skips that save-buffer call. > I have formatted 2 patches to address this (attached). If they look fine, I can commit them to master. 0001-Revert-org-capture-Do-not-save-buffer-when-running-o.patch Description: Binary data 0002-Add-no-save-keyword-for-Org-capture-templates.patch Description: Binary data
Re: [O] [PATCH] org-capture: Add a custom to control save target file or not.
Hello Nicolas, While we are planning to cut Org 9.2 release this week, this one regression in the Org Capture and auto-saving behavior comes to my mind, that I think should be fixed. Summary: In Org 9.1.x, org-capture target files got auto-saved after C-c C-c when ending the capture. In Org master branch, that stopped happening. As per your last proposal, we should revert https://code.orgmode.org/bzg/org-mode/commit/b4422add3745c26ec3b2e11b8da425844b2e9d3d and then add a :no-save option that skips that save-buffer call. Past references: - https://lists.gnu.org/r/emacs-orgmode/2018-04/msg00204.html - https://lists.gnu.org/r/emacs-orgmode/2018-09/msg00325.html -- Kaushal Modi On Sat, Sep 29, 2018 at 6:36 AM Van L wrote: > > >> Then saving should be the default again, and not saving optional. > > > > I believe this would be the best option. > > Very, very strongly concur with this belief. > >
Re: [O] [Bug?] org-20181210 seems to break Column View
Hello, Akater writes: > I've been using Column View for quite some time without any > issues. After today's update, C-c C-c on the BEGIN line of the dynamic > block > > #+BEGIN: columnview :hlines 1 :id local :maxlevel 3 > > [...] > > #+END: > > draws the table close to the very beginning of a buffer, starting at the > 11th char, cells determined by forumlas are left empty, the dynamic > block is emptied as well (so e.g. a TBLFM statement is gone). > > I'm quite sure it happened in recent hours, as I perform Column View > refresh several times a day. FWIW, I cannot reproduce it on master branch. Regards, -- Nicolas Goaziou
Re: [O] Bug: Special property ITEM without stars [9.1.14]
Allen Li writes: > On Wed, Dec 12, 2018 at 10:00 AM Nicolas Goaziou > wrote: >> >> This is not satisfying, actually. If every item has a single asterisk, >> you miss hierarchy between headlines in the same tree. > > I don't know what you mean. Hierarchy is not displayed normally in > agenda view anyway, I don't know why displaying it in agenda column > view via the ITEM property is desirable? > I use hierarchy in my custom agenda view everyday. Please do not remove this feature. Thanks, Bernt
Re: [O] Mean of a column in a remote table
Hello Eric, Eric S Fraga writes: > That should have been @>, not @<. | Data | a | |---+| | mic_2_in_648_cell | #ERROR | #+tblfm: $2=remote($1,vmean(@2..@>)) and 'Cells in the region copied, use M-x org-table-paste-rectangle to paste them in a table.' in the Message buffer. Thanks, Roger
[O] Org-drill edit feature request
Hi, Making drill editing seems be very painful by the current way org-drill offers. I make a lot of notes on most of the drilled entries, as for now, 1). press e (or other key to reveal the collapsed headlines) , e twice to go back to the original buffer. 2) add notes. (Even more keys pressing: if i collapsed the headlines before calling org-drill, i need to press tab to show all the contents at current headline.) 3) call org-drill-resume to go back. I would like to consider more intuitive ways to edit the drill entries. How do you think the workflow below? 1) press e to switch to edit mode like "helm-swoop", which keeps exactly same narrow, child headline showing as before. 2) add the notes. 3) Ctrl-c Ctrl-s to resume. Do you think my workflow is more reasonable? And i would like to hear more advices about the idea above. Thanks. LLCC
Re: [O] Mean of a column in a remote table
That should have been @>, not @<. -- Eric S Fraga via Emacs 27.0.50, Org release_9.1.14-1034-gafcb1d
Re: [O] Mean of a column in a remote table
On Thursday, 13 Dec 2018 at 09:12, Roger Mason wrote: > #+tblfm: $2=remote($1,vmean(@2..@-1)) [...] > The second column of the upper table is intended to receive the mean of > table 'mic_2_in_648_cell'. Instead I get the error 'Row descriptor -1 > leads outside table'. Try @< instead of @-1? -- Eric S Fraga via Emacs 27.0.50, Org release_9.1.14-1034-gafcb1d
Re: [O] problem with export of #+BEGIN_src latex :results latex replace :exports results :eval t
On Thursday, 13 Dec 2018 at 11:55, Uwe Brauer wrote: > That is for babel. That is I have an org file, which contains matlab and > latex for the documentation. So I want to cite a reference. There is no > problem with citep if I don't have the latex in a src block. > > However as I said the fortification is much nicer if I put latex in a > src block. Yes but my point is that the line that has the citep: link is org syntax and should therefore not be in the LaTeX src block. Keep the equation in the src block but take that line to past the end of the block. -- Eric S Fraga via Emacs 27.0.50, Org release_9.1.14-1034-gafcb1d
[O] Mean of a column in a remote table
Hello, I _think_ this question has a simple answer, but I cannot find it. I need the mean of a column in a remote table. My current attempt looks like this: | Data | a | |---+---| | mic_2_in_648_cell | | #+tblfm: $2=remote($1,vmean(@2..@-1)) #+name: mic_2_in_648_cell | a | |---| | 28.886207 | | 28.900981 | | 28.886101 | | 28.900659 | | 28.900526 | | 28.886694 | | 28.886559 | | 28.90024 | | 28.900524 | | 28.900583 | | 28.886496 | The second column of the upper table is intended to receive the mean of table 'mic_2_in_648_cell'. Instead I get the error 'Row descriptor -1 leads outside table'. This is a cut down example that captures the essence. Thanks for any help. Roger GNU Emacs 26.1 (build 1, i386-portbld-freebsd11.2, GTK+ Version 3.22.29) Org mode version 9.1.13 (release_9.1.13-784-ged7d1d @ /home/rmason/.emacs.d/org-git/lisp/)
Re: [O] [PATCH] ox.el: Define subtitle macro
Hi Kaushal and all, >> master branch is meant to be released... at some point. For the record, >> I cannot do it myself. > > +1 It would be great to have Org 9.2 released! I plan to release it on saturday 22nd, thanks for the heads up. Also, I just signed a three-years contract in december, meaning that I will have more time to become a contributor again. All best, -- Bastien
[O] [FORGET] (was: how to insert a ref to an latex equation in an org file (reftex-reference?))
>>> "Uwe" == Uwe Brauer writes: > Hi Please forget my message, org-ref-helm-insert-ref-link does precisely what I was looking for. Sorry. smime.p7s Description: S/MIME cryptographic signature
[O] how to insert a ref to an latex equation in an org file (reftex-reference?)
Hi
Consider
* Equations with labels
Consider the following
\begin{equation}
\label{eq:ref-problem:1}
\int f dx=0
\end{equation}
As \ref{eq:ref-problem:1}
Is there any org command which is roughly equivalent to reftex-reference
for latex equations?
Re: [O] problem with export of #+BEGIN_src latex :results latex replace :exports results :eval t
>>> "Eric" == Eric S Fraga writes:
> On Thursday, 13 Dec 2018 at 08:30, Uwe Brauer wrote:
>> Hi
> [...]
>> ,
>> | * Test of the bibliography
>> | #+BEGIN_src latex :results latex replace :exports results :eval t
>> |
>> | \begin{equation}
>> | \label{eq:testbib:1}
>> | \int f dx =0
>> | \end{equation}
>> |
>> | see
>> | citep:tao08:_global
>> |
>> | #+END_src
>> |
>> `
> Why have the citep line within the src block? It's not LaTeX and is in
> fact org syntax.
That is for babel. That is I have an org file, which contains matlab and
latex for the documentation. So I want to cite a reference. There is no
problem with citep if I don't have the latex in a src block.
However as I said the fortification is much nicer if I put latex in a
src block.
smime.p7s
Description: S/MIME cryptographic signature
Re: [O] problem with export of #+BEGIN_src latex :results latex replace :exports results :eval t
On Thursday, 13 Dec 2018 at 08:30, Uwe Brauer wrote:
> Hi
[...]
> ,
> | * Test of the bibliography
> | #+BEGIN_src latex :results latex replace :exports results :eval t
> |
> | \begin{equation}
> | \label{eq:testbib:1}
> | \int f dx =0
> | \end{equation}
> |
> | see
> | citep:tao08:_global
> |
> | #+END_src
> |
> `
Why have the citep line within the src block? It's not LaTeX and is in
fact org syntax.
--
Eric S Fraga via Emacs 27.0.50, Org release_9.1.13-894-gf79545
