Re: [O] FW: [RFC] Link-type for attachments, more attach options
Hello, this feature seem to be very useful, what is this patch status? At 2018-10-21 15:53:38, "Gustav Wikström" wrote: Hi, I’ve attached a patch with some suggested additions to org-attach. Patch comments below. Please review. Kind regards Gustav ___ Patch comments: * Add new linktype "attached" for attachments A new linktype "attached" is added in order to reduce link-duplication when wanting to link to files in attached folders of nodes. This works for both ID-based attachments and ATTACH_DIR. Inline images will trigger also for attachments, as well as search-decorations in the links. The goal is to make the functionality for attached-links mirror file-links. * Add further options for ATTACH_DIR When working with ATTACH_DIR there are now a couple of new options available: - org-attach-dir-inherit-by-default - org-attach-dir-create-if-not-exist - org-attach-dir-relative Descriptions of them can be found in the commit for each new customization. * Documentation in org-manual Org-manual is updated with the new link-type as well as some minor cleanup in the documentation related to external links and attachments.
Re: [O] OT: gmane seems to be back
> Robert Pluim writes: > Colin Baxter writes: >>> Nick Dokos writes: >> >> > Achim Gratz writes: >> Am 30.10.2018 um >> 16:57 schrieb Nick Dokos: >>> For a couple of weeks, I had not >> been able to connect to gmane, >>> so I finally gave up and >> changed my preferences so that I could >>> receive the email from >> the list. I have not seen any >>> acknowledgement anywhere that >> it was down BTW - did anybody here >>> notice? Or was it just me? >> >> >> >> Plain NNTP wasn't down at all, but connections that use TLS >> >> stopped working some time ago and probably still don't work. >> >> > I have this in my .gnus.el: >> >> > (setq gnus-select-method '(nntp "news.gmane.org" > >> (nntp-open-connection-function nntp-open-tls-stream) > >> (nntp-port-number 563) ;; (nntp-port-number 119) > >> (nnir-search-engine gmane) )) >> >> My gnus works fine (always has) with just the first line. The >> nntp-open-tls-stream and port-numbers appear not to be >> required. And I thought gmane.org was could no longer be searched >> with nnir. > If you do that then you connect to port 119 using cleartext and > the connection is (potentially) upgraded using STARTTLS. Thatʼs > not the same as making a TLS connection to port 563. Whether this > matters for reading news is entirely a personal decision. I did not know this so many thanks for the information. > The gmane search interface is sadly indeed defunct. Shame :-( Best wishes,
Re: [O] OT: gmane seems to be back
Colin Baxter writes: >> Nick Dokos writes: > > > Achim Gratz writes: > >> Am 30.10.2018 um 16:57 schrieb Nick Dokos: > >>> For a couple of weeks, I had not been able to connect to gmane, > >>> so I finally gave up and changed my preferences so that I could > >>> receive the email from the list. I have not seen any > >>> acknowledgement anywhere that it was down BTW - did anybody here > >>> notice? Or was it just me? > >> > >> Plain NNTP wasn't down at all, but connections that use TLS > >> stopped working some time ago and probably still don't work. > > > I have this in my .gnus.el: > > > (setq gnus-select-method '(nntp "news.gmane.org" > > (nntp-open-connection-function nntp-open-tls-stream) > > (nntp-port-number 563) ;; (nntp-port-number 119) > > (nnir-search-engine gmane) )) > > My gnus works fine (always has) with just the first line. The > nntp-open-tls-stream and port-numbers appear not to be required. And I > thought gmane.org was could no longer be searched with nnir. If you do that then you connect to port 119 using cleartext and the connection is (potentially) upgraded using STARTTLS. Thatʼs not the same as making a TLS connection to port 563. Whether this matters for reading news is entirely a personal decision. The gmane search interface is sadly indeed defunct. Robert
Re: [O] OT: gmane seems to be back
> Nick Dokos writes: > Achim Gratz writes: >> Am 30.10.2018 um 16:57 schrieb Nick Dokos: >>> For a couple of weeks, I had not been able to connect to gmane, >>> so I finally gave up and changed my preferences so that I could >>> receive the email from the list. I have not seen any >>> acknowledgement anywhere that it was down BTW - did anybody here >>> notice? Or was it just me? >> >> Plain NNTP wasn't down at all, but connections that use TLS >> stopped working some time ago and probably still don't work. > I have this in my .gnus.el: > (setq gnus-select-method '(nntp "news.gmane.org" > (nntp-open-connection-function nntp-open-tls-stream) > (nntp-port-number 563) ;; (nntp-port-number 119) > (nnir-search-engine gmane) )) My gnus works fine (always has) with just the first line. The nntp-open-tls-stream and port-numbers appear not to be required. And I thought gmane.org was could no longer be searched with nnir. Best wishes,
Re: [O] [BUG] src_blocks - :wrap blocks not being overwritten
> On Oct 31, 2018, at 2:26 AM, Carlos García wrote: > > The bigger issue is that it "used to work". A few releases ago, wrapped > results could be correctly replaced when using ":results replace". I was > wondering if the change was intentional or a side-effect of something else. > This commit seems to be the one. | * d7940ae..: Nicolas Goaziou 2017-11-27 ob-core: Fix removal of elements after RESULTS I am guessing that not including special-blocks was an oversight. If you prepare a patch, it will likely be applied unless Nicolas sees an issue. Chuck
Re: [O] bibtex setup .dir-locals.el
That looks right. I have this in a .dir-locals.el file and when I use
org-ref, it only shows me references from that file.
;;; Directory Local Variables
;;; For more information see (info "(emacs) Directory Variables")
((org-mode
(org-ref-default-bibliography . ("./References.bib"))
(bibtex-completion-bibliography . ("./References.bib"
You do have to close the org-file, and then reopen it after you make
that file, and when I do that I am prompted whether to apply or ignore
the settings.
It might be simpler to just use a bibliography link in the file though:
bibliography:References.bib
ed...@openmail.cc writes:
> Hello,
>
> I would like to know how to set my ~References.bib~ as a dir-local variable
> for
> use with bibtex (org-ref, reftex). I have this in my ~.dir-locals.el~. It
> keeps
> showing the global list of references. Thanks!
>
> #+BEGIN_SRC emacs-lisp
> ;;; Directory Local Variables
> ;;; For more information see (info "(emacs) Directory Variables")
>
> (
>(org-mode
> (reftex-default-bibliography .
> ("/Class/Biomat/Hw/Project/References.bib"))
> (org-ref-default-bibliography .
> ("/Class/Biomat/Hw/Project/References.bib"))
> (bibtex-completion-bibliography .
> ("/Class/Biomat/Hw/Project/References.bib"))
> (org-ref-bibliography-notes .
> "/Class/Biomat/Hw/Project/report-biomat.org")
> (bibtex-completion-notes-path .
> "/Class/Biomat/Hw/Project/report-biomat.org")
> (org-ref-pdf-directory . "/Class/Biomat/Hw/Project/Media/")
> (bibtex-completion-library-path . "/Class/Biomat/Hw/Project/Media/")
> )
>
>(bibtex-mode
> (reftex-default-bibliography .
> ("/Class/Biomat/Hw/Project/References.bib"))
> (org-ref-default-bibliography .
> ("/Class/Biomat/Hw/Project/References.bib"))
> (bibtex-completion-bibliography .
> ("/Class/Biomat/Hw/Project/References.bib"))
>
> (org-ref-bibliography-notes
> .
> "/Class/Biomat/Hw/Project/report-biomat.org")
>
> (bibtex-completion-notes-path
> .
> "/Class/Biomat/Hw/Project/report-biomat.org")
>
> (org-ref-pdf-directory
> .
> "/Class/Biomat/Hw/Project/Media/")
>
> (bibtex-completion-library-path
> .
> "/Class/Biomat/Hw/Project/Media/")
> )
>)
> #+END_SRC
>
> As an example:
> #+BEGIN_EXAMPLE
> reftex-default-bibliography is a variable defined in ‘reftex-vars.el’.
> Its value is
> ("/Class/Biomat/Hw/Project/References.bib")
> Original value was nil
> Local in buffer report-biomat.org; global value is
> ("//Research/References.bib")
>
> This variable’s value is directory-local, set by the file
> ‘/Class/Biomat/Hw/Project/.dir-locals.el’.
>
> Documentation:
> List of BibTeX database files which should be used if none are specified.
> When ‘reftex-citation’ is called from a document which has neither a
> ‘\bibliography{..}’ statement nor a ‘thebibliography’ environment,
> RefTeX will scan these files instead. Intended for using ‘reftex-citation’
> in non-LaTeX files. The files will be searched along the BIBINPUTS or
> TEXBIB
> path.
>
> You can customize this variable.
> #+END_EXAMPLE
>
> My system
> #+BEGIN_SRC emacs-lisp
> (concat
>(emacs-version) "\n"
>(org-version) "\n"
>(org-ref-version))
> #+END_SRC
>
> #+RESULTS:
> : GNU Emacs 26.1 (build 1, x86_64-pc-linux-gnu, GTK+ Version 3.22.30)
> : of 2018-07-05
> : 9.1.14
> : org-ref: Version 1.1.1
>
> -
>
> ONLY AT VFEmail! - Use our Metadata Mitigator to keep your email out of the
> NSA's hands!
> $24.95 ONETIME Lifetime accounts with Privacy Features! 15GB disk! No
> bandwidth
> quotas!
> Commercial and Bulk Mail Options!
--
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
Re: [O] letterhead and signature in odt export
I went down the path of a custom latex style, with custom exporter some
years ago. At the time, I was head of our undergrad committee, and I had
to write a lot of memo style documents on department letterhead. This
setup allowed me to quickly write memos and export them to pdfs. I also
use this for other things like letters of recommendation these days. I
put each one in a separate file.
I defined this skeleton (which you run by typing M-x memo) that makes it
easy to get a memo started:
(define-skeleton memo
"CMU memo template"
nil
"#+LATEX_CLASS: cmu-memo
#+CC:
#+DEPARTMENT: Department of Chemical Engineering
#+FROM: John Kitchin
#+FROMNAME: John Kitchin
#+SIGNATURE-LINES: nil
#+SUBJECT: "_"
#+TO: "@"
#+latex_header: \\usepackage{setspace}
#+latex_header: \\doublespacing
Sincerely,
John Kitchin
* build :noexport:
[[elisp:(cmu-memo-export-to-pdf-and-open)]]
")
Other solutions include a yasnippet, tempo, ...
I wrote an exporter you can find at
https://github.com/jkitchin/scimax/blob/master/ox-cmu/ox-cmu-memo.el
that uses the keywords to fill in parts of the document template.
Finally, I adapted
http://pi.math.cornell.edu/ADMIN/Computers/latex-letterhead/culetter.sty
to put all the header/logo info in and made it into a latex package. The
main reason for this is that the logo file is in the package, so I don't
have to know its path, worry about moving it, etc.
Knowing what I know now, and now my needs are a little simpler, I guess
you could avoid the sty file and achieve this via the exporter. It
mostly depends on where you want the information to get from org to
latex. Since I have some information in org-format, the exporter is
needed I think.
Regarding where to learn LaTeX, https://en.wikibooks.org/wiki/LaTeX
seems pretty good, but probably it won't help you understand that sty
file! That is written in tex.
There are many ways to get something suitable, I hope this helps!
Matt Price writes:
> Hi again Chris!
>
> OK, so I understand a little bit of this. I would like to keep all my
> letters in subheadings in a single org doc, and just export once. This
> version requires a fair amount of latex in every subtree. It would be nicer
> if the exporter just took care of the latex for me and I didn't have to
> look at it while I'm composing (I know that's not an issue for you,
> Chris).
>
> Is my best option to create an export-derived-backend based on latex (I see
> that's what John K has done in scimax)? Or is the preferred method to
> create a new latex class (whatever that is -- really I have no idea) and
> add the header and closing lines to that?
>
> Also... where should I go to learn more about latex (I have beengoogling,
> I've found some places, am wondering what the *best* place is)? It appears
> I am approaching adulthood and am ready to learn how to use it, after years
> of resisting :-/
>
> m
>
> On Tue, Oct 30, 2018 at 11:56 AM ckelty ckelty wrote:
>
>> I don’t mess around with LibreOffice, but if you want to do it in Org,
>> this is what I do and it works fine. Some of the preamble is superfluous—
>> for various letters I’ve had to add other LaTeX packages….
>>
>> ck
>>
>>
>> >
>> >
>> >
>>
>> #+STARTUP: indent
>> #+LANGUAGE: en
>> #+OPTIONS: num:nil toc:nil ':t
>> #+AUTHOR: Your Name Here
>> #+EMAIL: Your Email Here
>> #+LATEX_HEADER: \usepackage[utf8]{inputenc}
>> #+LATEX_HEADER: \usepackage[T1]{fontenc}
>> #+LATEX_HEADER: \usepackage{graphicx}
>> #+LATEX_HEADER: \usepackage{float}
>> #+LATEX_HEADER: \usepackage{wrapfig}
>> #+LATEX_HEADER: \usepackage{rotating}
>> #+LATEX_HEADER: \usepackage[normalem]{ulem}
>> #+LATEX_HEADER: \usepackage{hyperref}
>> #+LATEX_HEADER: \usepackage{setspace}
>> #+LATEX_HEADER: \usepackage{libertine}
>> #+LATEX_HEADER: \usepackage[left=1.5in,right=1.5in]{geometry}
>> #+LATEX_HEADER: \setlength{\parskip}{1em}
>> #+LATEX_HEADER: \setlength{\parindent}{0pt}
>>
>> # Insert your graphic here-- getting the scale right can take some work
>> \includegraphics[scale=0.145]{Your LetterHead PNG/JPG}
>>
>> \hfill \today
>>
>> [ Greeting Here ]
>>
>> # I use setspace and onehalfspacing to control line spacing
>> \onehalfspacing
>>
>> [ Insert Inflated Rhetoric About Here ]
>>
>> Yours sincerely,\\
>>
>> # Insert your sig here... ditto on scale.
>> \includegraphics[scale=0.4]{Your Sig PNG/JPG}
>>
>> \textbf{Your Name}\\
>> Illustrious Title\\
>> Second Illustrious Title\\
>> Etc.\\
>>
>>
>> <
>> <
>> <
>>
>> > On Oct 30, 2018, at 7:29 AM, Jeff Filipovits
>> wrote:
>> >
>> > Would you mind sharing them? This is a problem I am trying to figure out
>> as well.
>> >
>> > On Tue, Oct 30, 2018, 9:29 AM Eric S Fraga wrote:
>> > Matt,
>> >
>> > I've replied directly to you with some files.
>> > --
>> > Eric S Fraga via Emacs 27.0.50, Org release_9.1.13-783-g97fac4
>> >
>>
>>
--
Professor John Kitchin
Doherty Hall A207F
Department of Chemical Engineering
Carnegie Mellon University
Pittsburgh, PA 15213
412-268-7803
@johnkitchin
Re: [O] OT: gmane seems to be back
Achim Gratz writes: > Am 30.10.2018 um 16:57 schrieb Nick Dokos: >> For a couple of weeks, I had not been able to connect to gmane, so I >> finally gave up and changed my preferences so that I could receive the >> email from the list. I have not seen any acknowledgement anywhere >> that it was down BTW - did anybody here notice? Or was it just me? > > Plain NNTP wasn't down at all, but connections that use TLS stopped > working some time ago and probably still don't work. I have this in my .gnus.el: --8<---cut here---start->8--- (setq gnus-select-method '(nntp "news.gmane.org" (nntp-open-connection-function nntp-open-tls-stream) (nntp-port-number 563) ;; (nntp-port-number 119) (nnir-search-engine gmane) )) --8<---cut here---end--->8--- and that works now, but did not work for a while earlier in the month (or perhaps longer). IIUC what you said, port 119 with some other setting (nntp-open-network-stream perhaps, or nntp-open-plain-stream) for the connection function would have worked during this time? I'll have to remember that for next time... Thanks! -- Nick "There are only two hard problems in computer science: cache invalidation, naming things, and off-by-one errors." -Martin Fowler
Re: [O] Bug: clocktable thinks Oct 29 is Oct 28 [9.1.14 (release_9.1.14-1012-g643481 @ /home/unhammer/src/org-mode/lisp/)]
Kevin Brubeck Unhammer čálii: [...] > I see the same on org-mode > 9.1.9 (bundled with Emacs 26.1) or 9.1.12 and 9.1.14 from melpa-stable, > gnu elpa. > > I do *not* see this in 8.2.10 bundled with Emacs 25.3.2. git bisect tells me 8c7a14a850e7b988fe4c9d0eea9207793e2af368 introduced this. signature.asc Description: PGP signature
Re: [O] [BUG] src_blocks - :wrap blocks not being overwritten
Hi Chuck, The `drawer' option is enough to "wrap" results, but it fails to provide the customizability that `special-blocks' offer. For example, `special-blocks' can be iterated with `org-element-map'. From the point of view of theming, wrapped results use faces, such as `org-block-begin-line' than can be nicely customized. The bigger issue is that it "used to work". A few releases ago, wrapped results could be correctly replaced when using ":results replace". I was wondering if the change was intentional or a side-effect of something else. Regards, Carlos On Tue, Oct 30, 2018 at 4:24 PM Berry, Charles wrote: > > > > On Oct 30, 2018, at 3:35 AM, Carlos García wrote: > > > > Hi Chuck, > > > > Thanks for looking into this. How difficult/desirable would it be to > create another block such as "wrap-block" for those blocks created with > ":wrap"? > > A `special-block' is a syntactic element. A `wrap-block' is not. > > > > That way, the needed change would be rather elegant: > > > > :line 2478 of ob-core.el: > > | ;; Possible results types. > > | '(drawer example-block export-block fixed-width item > > | plain-list src-block table wrap-block) > > > > What would the repercussions be if `special-block' is added to the list? > > > > Few, I think. But except for those special-blocks that have defined > actions they would be ignored upon export. > > the `results' special-block would be ignored, IIUC. > > I suspect what you want is a `drawer', which encloses results without > further consequences that example blocks or export blocks impose. > > HTH, > > Chuck > > >
[O] Bug: clocktable thinks Oct 29 is Oct 28 [9.1.14 (release_9.1.14-1012-g643481 @ /home/unhammer/src/org-mode/lisp/)]
Hi, I did $ git clone https://code.orgmode.org/bzg/org-mode.git (which got me 643481fade386aa51d88ccc22b9669b0b77daaa1 ) $ cd org-mode $ make autoloads $ emacs -Q -l /tmp/init.el /tmp/foo.org where /tmp/init.el has: (add-to-list 'load-path "~/src/org-mode/lisp") (require 'org) and /tmp/foo.org has: #+STARTUP: showall * Top #+BEGIN: clocktable :maxlevel 3 :tstart "2018-10-01" :tend "2018-11-01" :step day :stepskip0 t #+END: ** TODO Undeobfuscate widget :LOGBOOK: CLOCK: [2018-10-29 må. 14:17]--[2018-10-29 må. 14:35] => 0:18 :END: ** DONE Deobfuscate widget :LOGBOOK: CLOCK: [2018-10-28 su. 14:17]--[2018-10-28 su. 14:35] => 0:18 :END: and then, on the BEGIN line, I did C-c C-c. This gave me: #+STARTUP: showall * Top #+BEGIN: clocktable :maxlevel 3 :tstart "2018-10-01" :tend "2018-11-01" :step day :stepskip0 t Daily report: [2018-10-28 su.] | Headline | Time | | |++--| | *Total time* | *0:18* | | |++--| | Top| 0:18 | | | \_ Deobfuscate widget || 0:18 | Daily report: [2018-10-28 su.] | Headline | Time | | |--++--| | *Total time* | *0:18* | | |--++--| | Top | 0:18 | | | \_ Undeobfuscate widget || 0:18 | #+END: ** TODO Undeobfuscate widget :LOGBOOK: CLOCK: [2018-10-29 må. 14:17]--[2018-10-29 må. 14:35] => 0:18 :END: ** DONE Deobfuscate widget :LOGBOOK: CLOCK: [2018-10-28 su. 14:17]--[2018-10-28 su. 14:35] => 0:18 :END: The second date is 28, where it should be 29. I see the same on org-mode 9.1.9 (bundled with Emacs 26.1) or 9.1.12 and 9.1.14 from melpa-stable, gnu elpa. I do *not* see this in 8.2.10 bundled with Emacs 25.3.2. The bug is also there without ":stepskip0 t" Emacs : GNU Emacs 25.3.2 (x86_64-pc-linux-gnu, GTK+ Version 3.22.29) of 2018-04-19 Package: Org mode version 9.1.14 (release_9.1.14-1012-g643481 @ /home/unhammer/src/org-mode/lisp/) current state: == (setq org-tab-first-hook '(org-babel-hide-result-toggle-maybe org-babel-header-arg-expand) org-speed-command-hook '(org-speed-command-activate org-babel-speed-command-activate) org-occur-hook '(org-first-headline-recenter) org-metaup-hook '(org-babel-load-in-session-maybe) org-confirm-shell-link-function 'yes-or-no-p org-after-todo-state-change-hook '(org-clock-out-if-current) org-src-mode-hook '(org-src-babel-configure-edit-buffer org-src-mode-configure-edit-buffer) org-agenda-before-write-hook '(org-agenda-add-entry-text) org-babel-pre-tangle-hook '(save-buffer) org-mode-hook '((closure (org--rds reftex-docstruct-symbol orgtbl-line-start-regexp org-element-greater-elements org-table-coordinate-overlays org-table-auto-blank-field org-clock-history org-agenda-current-date org-with-time org-defdecode org-def org-read-date-inactive org-ans2 org-ans1 org-columns-current-fmt-compiled org-clock-current-task org-clock-effort org-agenda-skip-function org-agenda-skip-comment-trees org-agenda-archives-mode org-end-time-was-given org-time-was-given org-log-note-extra org-log-note-purpose org-log-post-message org-last-inserted-timestamp org-last-changed-timestamp org-entry-property-inherited-from org-blocked-by-checkboxes org-state org-agenda-headline-snapshot-before-repeat org-capture-last-stored-marker org-agenda-start-on-weekday org-agenda-buffer-tmp-name clean-buffer-list-kill-buffer-names org-id-link-to-org-use-id org-agenda-buffer-name org-priority-regexp buffer-face-mode-face org-mode-map org-tbl-menu org-org-menu org-struct-menu org-entities org-last-state org-id-track-globally org-clock-start-time texmathp-why remember-data-file org-agenda-tags-todo-honor-ignore-options iswitchb-temp-buflist calc-embedded-open-mode calc-embedded-open-formula calc-embedded-close-formula align-mode-rules-list org-emphasis-alist org-emphasis-regexp-components org-export-registered-backends org-modules org-babel-load-languages org-indent-indentation-per-level org-element-paragraph-separate ffap-url-regexp org-inlinetask-min-level t) nil (add-hook (quote change-major-mode-hook)
Re: [O] OT: gmane seems to be back
Am 30.10.2018 um 16:57 schrieb Nick Dokos: For a couple of weeks, I had not been able to connect to gmane, so I finally gave up and changed my preferences so that I could receive the email from the list. I have not seen any acknowledgement anywhere that it was down BTW - did anybody here notice? Or was it just me? Plain NNTP wasn't down at all, but connections that use TLS stopped working some time ago and probably still don't work. -- Achim. (on the road :-)
Re: [O] Help with sharing emacs-org presentation
On 2018-10-25, Feiming Chen wrote: > I gave a talk on emacs-org in a local workshop (Government Advances > in Statistical Programming) in Washington D.C. yesterday. I'd like to > share the slides and org source file with the community (see attached). Thanks for sharing! I wonder why you stress the following: - Not good for collaborative use (unlike Microsoft Office). - Good for private, non-collaborative use. My view is the opposite: Org mode is excellent for collaboration as it is plain text, suitable for diff/merge in Git repositories. Thanks to the separation of contents from style, cross-organizational collaboration is possible, which I find *very* hard with any office tool: Changing a document master leads to all kinds of layout destruction. Switching to a different corporate identity is just hard with what-you-see-is-what-you-get tools. In contrast, Org mode can be a basis for what is called Single Sourcing [1] in the context of technical writing. You can see my approach towards Open Educational Resources with Org mode at [2]. Best wishes Jens [1] http://rockley.com/articles/Single_Sourcing_and_Technology.pdf [2] https://gitlab.com/oer/OS
