Re: [O] [PATCH] org-sort: Read compare-func in interactive calls
Nicolas Goaziou writes: >> * lisp/org-list.el (org-sort-list): Read COMPARE-FUNC when called >> interactively rather than being restricted to the default behavior of >> sort-subr's PREDICATE parameter. Guard prompts for GETKEY-FUNC and >> COMPARE-FUNCTION with called-interactively-p, like >> org-table-sort-lines already did for GETKEY-FUNC. > > Thank you. I have but one comment. Thanks for taking a look. >> + (sort-func >> + (cond >> + ((= dcst ?a) #'string<) >> + ((= dcst ?f) >> +(or compare-func >> +(and (called-interactively-p 'any) > > The above should be avoided. See `called-interactively-p' docstring. The > same applies in other places. Yeah, in order to make org-sort-entries, org-sort-list, and org-table-sort-lines behave the same way with respect to how they read getkey-func and compare-func, I ignored the warning in called-interactively-p's docstring that says it can be "brittle" if a function is advised or being debugged. Instead of adding called-interactively-p to org-sort-entries and org-sort-list, I initially looked at removing called-interactively-p from org-table-sort-lines, but I think that would 1) require changing its behavior for determining the sorting column, and 2) going against org-table-sort-lines's docstring that says no prompting will take place if called from Lisp. So I'm fine removing called-interactively-p from org-table-sort-lines, but I'm not sure how it should behave, particularly with respect to the column prompt. Thoughts? -- Kyle
[O] org-export-filter-final-output-functions
I want to setq org-export-filter-final-output-functions on per project
basis, is it possible?
I have #+INCLUDE: blog-header.inc in my org file with content:
#+BEGIN_EXPORT html
{{blog_header}}
{{blog_subheader}}
Posted by nullx002
on {{blog_date}}
#+END_EXPORT
in my init file I have following:
(defun nullx002/org-blog-set-filter (output backend info)
"required to publish dynamic blog post headers from org-journal"
(setq output (replace-regexp-in-string "{{blog_img}}" (read-input "Image: ")
output ))
(setq output (replace-regexp-in-string "{{blog_header}}" (read-input "Head:
") output ))
(setq output (replace-regexp-in-string "{{blog_subheader}}" (read-input
"SubHeader: ") output ))
(setq output (replace-regexp-in-string "{{blog_date}}" (format-time-string
"%a, %b %d, %Y") output ))
output
)
(setq org-export-filter-final-output-functions '(nullx002/org-blog-set-filter))
It serves me well in replacing those entries from mini buffer for
journal/blog entries with M-x org-publish-current-file Only problem is
that function (org-export-filter-final-output-function) is universal and
asks for image, header, etc. for all org-files.
I want it only for a certain project with org-journal and not all
org-projects in (org-publish-project-alist). I have tried
:publishing-function but it doesn't work.
Is it even possible?
Thanks
--
~nullx002 (somewhere on pale blue dot)
github.com/nullx002
bitbucket.org/nullx002
twitter.com/nullx002
Re: [O] No contrib directory in org-plus-contrib package
On Wed, May 3, 2017, 7:10 AM Roland Everaert wrote: > Hi, > > I have installed org-mode from ELPA and choose to install the version with > the contribution, but the directory is missing in the org-plus-contrib > package directory, and the docs directory as well. > > Have I missed something or is their something screwed in the build of the > package? > > I use Emacs 25.2.1 on cygwin 64bit. > All packages from the contrib/ dir are at the base dir level in the installed org-plus-contrib package dir. Basically the dir structure is flattened out when you install that package. > -- Kaushal Modi
Re: [O] Bug: Bulk reschedule with reschedule logging on fails
Hello, Allen Li writes: > Allen Li writes: > >> I can think of three reasonable options: >> >> 1. Prompt for a note, then apply it to all affected items. >> 2. Prompt for a note, then apply it only to items that are already >>scheduled (and hence rescheduled). >> 3. Don't attempt to add a note and just add timestamps. > > Nicolas Goaziou writes: > >> It is fixed, with option 3. Global note doesn't sound like a silver >> bullet. Also, 3 was much easier to implement. > > I believe that this bug has not been fixed for ‘org-log-redeadline’ as I > have encountered it recently, but I have not done a clean repro of it > yet (although I think such a repro may not be necessary). Correct. Fixed, this time. Thanks for the heads-up. Regards, -- Nicolas Goaziou
Re: [O] Bug: Multiple bulk actions on the same task fails [9.0.5 (9.0.5-elpaplus @ /Users/links_world/.emacs.d/elpa/org-plus-contrib-20170210/)]
Hello, Adrian Bradd writes: > Using the following agenda file as an MWE: > > * Incoming > ** TODO Testing1 > ** TODO Testing2 > ** TODO Testing3 > > I ran org-agenda and pressed 't' to list all todo items. In the agenda > buffer I marked the task 'Testing1' with 'm' and performed a bulk action with > 'B' and > added a tag with '+'. This completed successfully. If I mark "Testing1' > again with 'm' and use 'B' to perform a bulk action I receive an error: > > user-error: Marker # for bulk > command is invalid > > If I close out of the agenda buffer and open it back up again I am able > to perform a bulk action on any entry. Fixed. Thank you. Regards, -- Nicolas Goaziou
Re: [O] [PATCH] org-sort: Read compare-func in interactive calls
Hello, Kyle Meyer writes: > * lisp/org-macs.el (org-read-function): New function. > * lisp/org.el (org-sort-entries): > * lisp/org-table.el (org-table-sort-lines): > * lisp/org-list.el (org-sort-list): Read COMPARE-FUNC when called > interactively rather than being restricted to the default behavior of > sort-subr's PREDICATE parameter. Guard prompts for GETKEY-FUNC and > COMPARE-FUNCTION with called-interactively-p, like > org-table-sort-lines already did for GETKEY-FUNC. Thank you. I have but one comment. > + (sort-func > + (cond > +((= dcst ?a) #'string<) > +((= dcst ?f) > + (or compare-func > + (and (called-interactively-p 'any) The above should be avoided. See `called-interactively-p' docstring. The same applies in other places. Regards, -- Nicolas Goaziou
Re: [O] Support for vertical writing directly in Org Mode
Is this just for Latex export? If so, this should already work for you.
#+latex_header: \usepackage{pdflscape}
#+BEGIN_landscape
test
#+END_landscape:
> Hello, Org Mode Community,
>
> I have done some quick search, but so far it seems that org mode does not
> really support exporting written text in a horizontal (that is landscape)
> direction
>
> Would a feature like this be possible in the future? For example:
>
> #+BEGIN_VERTICAL
>
> Some text written in a typical horizontal/portrait fashion, but is rendered
> vertically upon export when inside these tags.
>
> #+END_VERTICAL
>
> Or maybe it should be called #+BEGIN_LANDSCAPE / #+END_LANDSCAPE, I am not
> sure :).
>
> Thanks for all your time and help,
> Marek
--
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] stable org-plus-contrib
On Thu, May 11, 2017 at 9:20 AM Phillip Lord wrote: > Kaushal Modi writes: > > I'm afraid that I didn't note them carefully enough to report. I just > assumed I was on a unstable version. Stable or not, a bug report would be always welcome.. that will help the unstable become stable :) I can cope with being on an > something unstable in general, but don't really have the time to do this > for org also. > I can understand that, but really the master branch hasn't been that "unstable" for me. > Okay, so the last point release with bug fixes? It should be version > 9.0 essentially? > It's the latest stable release (not necessarily a point release) plus bug fixes. The latest release as of today is 9.0.6 ( http://orgmode.org/cgit.cgi/org-mode.git/log/?h=maint ). > New big features get added to the master (devel) branch. > > > > That said, I have been using the master branch as my daily driver for > over > > a year. As of now I don't see any bug that affects my workflow. > > Well, you'd probably fix it if there was:-) Well, most of the times, I just report them. The org dev community is very active and a reported bug usually gets fixed in a day or two. -- Kaushal Modi
Re: [O] stable org-plus-contrib
Kaushal Modi writes: > On Thu, May 11, 2017, 8:20 AM Phillip Lord > wrote: > >> >> Really? That's rather confusing. So, it means that a bug here is a bug >> in a release version? >> > > Well, a bug's not a bug till it is seen :) > > What is the buggy behavior that you find in the Elpa version? I'm afraid that I didn't note them carefully enough to report. I just assumed I was on a unstable version. I can cope with being on an something unstable in general, but don't really have the time to do this for org also. > Simply put, the Melpa version has the latest weekly cut from the maint > branch (minus the contrib packages), the org Elpa version is the same but > with contrib packages. So those are stable versions. If one finds a bug in > those, then they get fixed when reported. Okay, so the last point release with bug fixes? It should be version 9.0 essentially? > New big features get added to the master (devel) branch. > > That said, I have been using the master branch as my daily driver for over > a year. As of now I don't see any bug that affects my workflow. Well, you'd probably fix it if there was:-) Phil
Re: [O] stable org-plus-contrib
On Thu, May 11, 2017, 8:20 AM Phillip Lord wrote: > > Really? That's rather confusing. So, it means that a bug here is a bug > in a release version? > Well, a bug's not a bug till it is seen :) What is the buggy behavior that you find in the Elpa version? Simply put, the Melpa version has the latest weekly cut from the maint branch (minus the contrib packages), the org Elpa version is the same but with contrib packages. So those are stable versions. If one finds a bug in those, then they get fixed when reported. New big features get added to the master (devel) branch. That said, I have been using the master branch as my daily driver for over a year. As of now I don't see any bug that affects my workflow. > -- Kaushal Modi
[O] Support for vertical writing directly in Org Mode
Hello, Org Mode Community, I have done some quick search, but so far it seems that org mode does not really support exporting written text in a horizontal (that is landscape) direction Would a feature like this be possible in the future? For example: #+BEGIN_VERTICAL Some text written in a typical horizontal/portrait fashion, but is rendered vertically upon export when inside these tags. #+END_VERTICAL Or maybe it should be called #+BEGIN_LANDSCAPE / #+END_LANDSCAPE, I am not sure :). Thanks for all your time and help, Marek
Re: [O] stable org-plus-contrib
Michael Alan Dorman writes: > phillip.l...@russet.org.uk (Phillip Lord) writes: >> I would like to use some of the packages in org-plus-contrib. So, I've >> added orgmode's ELPA archive. But I find being on the bleeding edge a >> little buggy. >> >> As far as I can see, there is no "stable" ELPA package archive, so I >> have to fall back installation from git. This seems somewhat backward to >> me; installing stable with git, an unstable from package.el. >> >> Is there any way of getting stable Org that I am missing? > > FWIW, the versions in the org ELPA repository, though date-versioned, > appear to only be generated for tagged versions. Really? That's rather confusing. So, it means that a bug here is a bug in a release version? Phil
Re: [O] [RFC] The "c" Org macro
On Monday, 8 May 2017 at 16:52, Nicolas Goaziou wrote:
> Here is an updated patch, in which one can write
>
> {{{c(sub,reset)}}}
> {{{c(sub, 5)}}}
>
> or even, for the default macro
>
> {{{c(,reset)}}}
> {{{c(, 99)}}}
Finally found some time to try the patch out. All of the above work
very well.
thanks,
eric
--
: Eric S Fraga (0xFFFCF67D), Emacs 26.0.50, Org release_9.0.6-432-g6fee6b.dirty
signature.asc
Description: PGP signature
