Re: Clocktable parameters
Colin Baxter writes: > I find the differences between the variables > > (1) org-clocktable-defaults > (2) org-agenda-clockreport-parameter-plist > > hard to understand. > > Ok, (1) seems reasonably clear. It's described in `info' (there's no > doc-string). The variable (2) confuses me. According to its doc string > (there's no `info' mention) it gives parameters for a clock table in > the daily and weekly agendas. How is that different from (1)? > > Am I correct in thinking (1) is primarily for a clock table not > associated with the agenda? Quite how such a clocktable would arise is > unclear to me. 8.4.2 The clock table section of the manual described the clocktables you can create inside Org buffers. org-clocktable-defaults apply for those clocktables. org-agenda-clockreport-parameter-plist only applies to org-agenda-clockreport-mode inside agenda views. org-clocktable-defaults is disregarded inside Org agendas. Best, Ihor
Re: Org and Hyperbole
Samuel Wales writes: > thanks! i was aware that it was developed on github, but i do not > know anything about github, and didn't kow if there was a maliing list > in addition. or are projects given their own mailing lists when they > are formed on github? or is there an email bidir interface to github? > or is pretty much absolutely everything for such projects done on > gh's website and you hae to have an account to ask a q? i might be > asking too much of gh :). Github is not very FSF-friendly. AFAIK, you must have an account to participate in the discussions. In order to make an account, you also need to run a non-Free JS. To post a question, you usually have to open an "issue" on the website. Though you can leverage Magit to do it for you without browser. (https://magit.vc/manual/forge/) Tracking new "issues" is somewhat easier - you can make Github send emails to you and you can reply to those emails normally - the replies will show up as "comments" in Github page. Also, once you created an issue, you can reply by email if you configured Github to send you email updated. Best, Ihor
Re: Org and Hyperbole
thanks! i was aware that it was developed on github, but i do not know anything about github, and didn't kow if there was a maliing list in addition. or are projects given their own mailing lists when they are formed on github? or is there an email bidir interface to github? or is pretty much absolutely everything for such projects done on gh's website and you hae to have an account to ask a q? i might be asking too much of gh :). On 7/1/22, Ihor Radchenko wrote: > Samuel Wales writes: > >> is there a mailing list for embark? > > AFAIK, embark is developed on GitHub: > https://github.com/oantolin/embark/ > > Best, > Ihor > -- The Kafka Pandemic A blog about science, health, human rights, and misopathy: https://thekafkapandemic.blogspot.com
Re: Org and Hyperbole
Samuel Wales writes: > is there a mailing list for embark? AFAIK, embark is developed on GitHub: https://github.com/oantolin/embark/ Best, Ihor
Re: [BUG] Incorrect background color [9.5.4 (release_9.5.4-3-g6dc785 @ /Users/salutis/src/emacs/nextstep/Emacs.app/Contents/Resources/lisp/org/)]
Rudolf Adamkovič writes: > The Org Babel R documentation at > > https://orgmode.org/worg/org-contrib/babel/languages/ob-doc-R.html > > says that > >> the background color defaults to "transparent" > > but it defaults to white. Confirmed. WORG page is not accurate here. The truth is that ob-R.el does not provide any defaults for header args. Instead, R defaults are used. I suspect that defaults for background color changed in R since the WORG page has been written. Best, Ihor
Re: Org and Hyperbole
is there a mailing list for embark? On 6/24/22, Robert Weiner wrote: > Hi João: > > Oantolin no doubt can speak to Embark much better but my present > understanding is that it is a toolkit package for generating contextual > popup or completion menus with a few standard context menus included. > > Hyperbole is a much broader personal information management > environment, one part of which is to turn every common type of > cross-reference found in buffers from programming identifiers to > page links into immediately useable hyperlinks with no effort > or markup on your part (implicit buttons). > > Hyperbole includes a large array of implicit buttons and context > awareness, rather than expecting you to write your own solutions > to all of your needs. It is more turn-key. One appendix in the > Hyperbole manual is filled with all the contexts and associated > actions that Hyperbole supports out of the box: > > https://www.gnu.org/software/hyperbole/man/hyperbole.html#toc-Smart-Key-Reference-1 > > Other features include: named hyperbuttons accessed from any > buffer, advanced contact management or hierarchical record > searching (point HyRolo at Org files and you can find single > entries within hierarchies), automatable frame and window > management, action triggers from mouse drags, Org hyperbutton > activation outside of Org mode, easy menu-based exposure of > Emacs filtering and searching capabilities, quick grid-based > display of desired buffers or files. Hyperbole puts your textual > information at your fingertips in a myriad of ways, just as Emacs > makes text editing convenient and flexible in a myriad of ways. > > Like Emacs, you are expected to grow into a broad away of uses across time, > not to digest all at once or in your first month of use. But by learning > and combining > capabilities, you can become masterful at managing your information and Org > can > be a big part of this journey as well. > > Enjoy. > > -- rsw > > > On Fri, Jun 24, 2022 at 1:57 PM João Pedro > wrote: > >> Hey Robert. Thanks for coming here to offer to clarify any doubts people >> have regarding Hyperbole. >> >> I haven't been interacting with the thread, but I've been lurking about >> and I've tried Hyperbole in the past, but couldn't precisely figure out >> its use case in my particular workflow, so I gave up on it. >> >> Now, according to your description, the main feature of Hyperbole looks >> a lot like what Embark [1] does sort of the same thing, albeit in >> different contexts, complexity (not a bad thing) and workflow. Would you >> be able to compare them? I think it would help me understand where >> exactly Hyperbole fits, and what is the problem it tries to solve. >> >> [1] https://github.com/oantolin/embark >> >> Best regards, >> >> -- >> João Pedro de A. Paula >> IT undergraduate at Universidade Federal do Rio Grande do Norte (UFRN) >> > -- The Kafka Pandemic A blog about science, health, human rights, and misopathy: https://thekafkapandemic.blogspot.com
Re: [PATCH] oc-csl: Add support for nocite citations
András Simonyi writes:
> the attached patch adds support for nocite citations in the csl
> org-cite export processor, including support for using the special key
> "*" to include all entries in the bibliography.
Thanks!
By "*", do you mean something like [cite/n:@*]?
If so, will it be correctly fontified as an existing citation?
> +*** Support for nocite citations in the csl export processor
>
> +The csl citation export processor now supports `nocite' style
> +citations that add items to the printed bibliography without visible
> +references in the text. Using the key `*' in a nocite citation
> +includes all available items in the printed bibliography.
It would help to provide an example how to use "*" key.
Also, I'd prefer if you follow doc/Documentation_Standards.org. Please
use Org markup instead of `...' quotes.
> +(defun org-cite-csl--nocite-p (citation info)
> + "Non-nil when CITATION object's style is nocite.
> +INFO is the export state, as a property list."
> + (when-let ((style (car (org-cite-citation-style citation info
> +(or (string= style "nocite") (string= style "n"
Why not simply
(member (car (org-cite-citation-style citation info)) '("nocite" "n"))
?
Best,
Ihor
sorting plain list while making - equal spc [was Re: [O] About org-sort -> org-sort-list with custom sort function]
i am confused by the custom sorting function for plain lists. are there examples? [note: still on maint.] i want to ignore [-] for sorting by checked. it can be equal to [ ]. i don't need it to be custom but that seems available. a rationale and possible interesting solutions are below, but i'm ok with anything. current x/X is always flawed for me. rationale: suppose you have a long list like - [ ] hello + [ ] hi + [ ] greetings ... [long list] suppose you mark greetings as [X] with c-c c-c, at least with my settings, hello will become [-] to indicate "partly X". suppose hello is still high priority. but you don't notice it's there because you use very large fonts and it is not on the same page. it's in the middle. you keep your list in priority sequence. you have at the top something like - [ ] bonjour - [ ] some kind of greeting ... and most are spc like that and - is rare. suppose you mark bonjour X with c-c c-c. now it is in your face and you want to move it down. so you sort by checked. now it is out of your face. but you didn't notice that your hello moved down also. this isn't particularly a bug; it is just that - is part of sorting and it is hardcoded to be below SPC [i think]. so hello gets moved down a whoole lot. its place in the list is gone. you aren't even looking at the bottom of hte list because it is so long. it is as if hello has disappeared. and this is because you marked a sub-item as X. and then sorted the top level by checked. and didn't notice. so i'm thinking this is a feature that could cause unexpected results. [because it did that to me. existence proof.] and there's nothing really wrong with existing semantics, but i'd want - to be ignored in sorting, because of the above. i can think of some possible solutions. for example - have something like an x X command that makes - eqal to spc or custom variable for sorting with ability to specify '(? ?x) thus ignoring ?-. - have a command that moves all X to a sibling header so you don't need sorting to get X out of your face - have the possibility of this all working on sublists too [i kinda want all there are more ideas. please do not shoot me or say i am destroying the spirit and letter of org and the milky way galaxy. these are just brainstorms. possibilities to possibly consider, not analyzed to perfection.] thanks! On 5/8/17, Kyle Meyer wrote: > Kyle Meyer writes: > >> Nicolas Goaziou writes: >> >>> The we may not need `call-interactively' at all. >>> >>> WDYT? >> >> Yeah, I agree that there's no need for call-interactively here because >> the interactive forms of org-table-sort-lines, org-sort-list, >> org-sort-entries are covered by org-sort's. >> >> Switched call-interactively to funcall in c1addc825. > > Ehh, I should have looked more closely at org-table-sort-lines. Unlike > org-sort-entries and org-sort-list, it uses called-interactively-p to > determine whether it should prompt the user. I've put the > org-call-with-arg back, at least for now. > > -- > Kyle > > -- The Kafka Pandemic A blog about science, health, human rights, and misopathy: https://thekafkapandemic.blogspot.com
Re: [PATCH] describe how to override Author
Robert Pluim writes: >> On Thu, 30 Jun 2022 21:19:36 +0800, Ihor Radchenko >> said: > > Ihor> Robert Pluim writes: > >> >> Occasional committers would probably not read org-maintenance.org, > and > >> >> those are the people this section is aimed at, I think. Plus itʼs > the > >> >> kind of thing you need to catch early: once the commit has been > pushed > >> >> itʼs too late. > >> > Ihor> Not really. org-contribute.org is the page directly linked from > Ihor> orgmode.org. It is aiming for new contributors with no write access. > >> > >> This particular change is in "Your first commit as an Org > >> maintainer". Perhaps that node should be moved to org-maintenance.org? > > Ihor> I do not think so. I am seeing this section as a "crash course" for > the > Ihor> new maintainers. We should only provide the critical information > there. > Ihor> Not too much, not too less. Something to not scare people with the > Ihor> details. > > I guess we disagree about whether knowing about the distinction > between 'Author:' and 'Commit:' is critical or not. For a free > software project correct attribution of changes is very important, so > committers should pay attention to it (and by extension the > documentation should educate them about it at the earliest > opportunity). But youʼre the maintainer :-) Maybe we are mis-communicating here. AFAIU, carefully checking Author: and Commit: is only relevant when applying commits made by people without commit access. Same goes for checking the copyright status of the patch authors. Occasional committers do not usually apply patches made by others. > Ihor> The elaborate details should be in org-maintenance.org, which is > Ihor> directly mentioned at the end of the "first commit" section. > > In "Where can I track bugs, patches and updates?" or somewhere else? I think that "Copyright assignments" is suitable. "keep track of copyright assignments" includes checking the copyright status of the patch authors. > BTW, Iʼm having trouble parsing this sentence from there: > > You don't much more: confirming bugs is a critical contribution. > > Thereʼs at least one word missing betweeen "donʼt" and "much" there. Fixed. Should be "You don't need to do much more: confirming bugs is a critical contribution." Best, Ihor
Re: [PATCH] Delete some Emacs 24 compat code
Stefan Kangas writes: > Thanks, please find attached an updated patch. Applied onto main via 0ed0dea22. Best, Ihor
Re: [PATCH] Improve formatting and documentation inline source block [9.3 (release_9.3 @ /usr/local/share/emacs/28.0.50/lisp/org/)]
Ihor Radchenko writes: > * doc/org-manual.org (Exporting Code Blocks): Clarify that results are > exported by default for inline source blocks. Applied onto main via 2d5274108. Best, Ihor
Re: Links to javascript-based websites from orgmode.org: Paypal and Github
Richard Stallman writes: > > Clarification: Links to Liberapay do work without running non-free > > software (you can try opening the link yourself). It is only the payment > > process that does not work. > > I am using metonymy, saying "the link works" to mean "the link's > functionality works." It makes the wording shorter, and everyone > can understand it -- including you, if you try. > > What purpose is served by refusing to understand? I did not refuse to understand. FYI, English is not my mother tongue and I sometimes miss fine details of the word meanings. I wrote the above reply because I was not 100% sure if you know the Liberapay web page itself does not run non-Free JS. Judging from this reply of yours, you do understand it, which means that my clarification did not serve much purpose for you, but should not heart the understanding. It could be useful though if I were right in my doubt. Note that my clarification did not imply that I propose to leave the current state of affairs with Liberapay not providing any non-free way to donate. In my other message I suggested to add some kind of postal address to allow users to donate by sending a check (a Free alternative). That way, users could go to Liberapay page and see the Free way to donate + non-free ways (which we should indicate as not recommended). Not every person is even aware how to use checks these days (I only sent a check once in my life and it was not straightforward). FYI, saying that GNU projects cannot ask for donations is quite upsetting and also discouraging. I'd prefer to find an ethically acceptable alternative. Best, Ihor
Re: [PATCH] Remove additional newline at end of results block
Matt Huszagh writes:
> + ;; We deliberately do not insert a newline here since there are
> + ;; valid cases in which a user does not want a blank line between a
> + ;; results block and the subsequent text.
>(beginning-of-line 0)
>(when hash (org-babel-hide-hash)))
Thanks for the patch! And sorry for the late reply.
Your explanation is quite confusing, but I think I managed to understand
what you referred to:
--
We can write the simplest equation as
#+begin_src latex :exports results
\begin{equation}
1 + 1 = 2,
\end{equation}
#+end_src
the paragraph should continue here.
will be exported as
--
We can write the simplest equation as
\begin{equation}
1 + 1 = 2,
\end{equation}
the paragraph should continue here.
--
Note the extra empty line below equation environment.
However, I am not confident if the proposed change is going to be safe
for other uses of src blocks.
I'd like to request other people who use export and source blocks
extensively to try the patch and see if it breaks anything.
Meanwhile, could you please reword the commit message and make it more
concise and clear?
Best,
Ihor
Re: Links to javascript-based websites from orgmode.org: Paypal and Github
[[[ To any NSA and FBI agents reading my email: please consider]]] [[[ whether defending the US Constitution against all enemies, ]]] [[[ foreign or domestic, requires you to follow Snowden's example. ]]] > Bank uses free software on their system? I suppose that would depend on the bank. It's the bank's affair. If the bank's software is free, the bank enjoys freedom. Otherwise, the nonfree software denies the bank freedom. Either way, it has no effect on us. We are not running that software, so it does not deny us our freedom. I would advise any bank to insist on free software, but if it doesn't listen, that is the bank's loss, not ours. I feel sorry for the bank for this error, but that is not a reason to boycott it. > Or are we to merely shift to services where nonfree software runs on > somebody else's computer? Who is morally responsible for running the nonfree software is the most important question, but you dismiss that as an insignificant detail. > Go to an internet kiosk and make the payment? That is a fune way way. However, I usually mail a check instead. It doesn't require me to run any nonfree software (it doesn't use software at all), and I can do it from home. -- Dr Richard Stallman (https://stallman.org) Chief GNUisance of the GNU Project (https://gnu.org) Founder, Free Software Foundation (https://fsf.org) Internet Hall-of-Famer (https://internethalloffame.org)
Re: Links to javascript-based websites from orgmode.org: Paypal and Github
[[[ To any NSA and FBI agents reading my email: please consider]]] [[[ whether defending the US Constitution against all enemies, ]]] [[[ foreign or domestic, requires you to follow Snowden's example. ]]] > Clarification: Links to Liberapay do work without running non-free > software (you can try opening the link yourself). It is only the payment > process that does not work. I am using metonymy, saying "the link works" to mean "the link's functionality works." It makes the wording shorter, and everyone can understand it -- including you, if you try. What purpose is served by refusing to understand? -- Dr Richard Stallman (https://stallman.org) Chief GNUisance of the GNU Project (https://gnu.org) Founder, Free Software Foundation (https://fsf.org) Internet Hall-of-Famer (https://internethalloffame.org)
[BUG] Incorrect background color [9.5.4 (release_9.5.4-3-g6dc785 @ /Users/salutis/src/emacs/nextstep/Emacs.app/Contents/Resources/lisp/org/)]
Hello everyone! The Org Babel R documentation at https://orgmode.org/worg/org-contrib/babel/languages/ob-doc-R.html says that > the background color defaults to "transparent" but it defaults to white. Just when I add ':bg transparent' to #+BEGIN_SRC R :results graphics file :file test.svg the plot becomes transparent. P.S. I use the plain old "plot" function, with no fancy R packages. Rudy -- "Genius is 1% inspiration and 99% perspiration." -- Thomas Alva Edison, 1932 Rudolf Adamkovič [he/him] Studenohorská 25 84103 Bratislava Slovakia
Re: Links to javascript-based websites from orgmode.org: Paypal and Github
My two cents on this: * Why not just have a single fallback person that takes the hit of having to use a JS based payment method in the meantime? * Or why not just keep the address and encourage mailing donations themselves to a single location (probably FSF office, no?) I might not know anything about how wiring money works in the context of requiring JS for the transactions, but I feel like if it were just one person to receive payment, or a single address, you could probably remove half of the problems as a result while Librepay becomes more readily available and less dependent on JS based payment APIs. Sincerely, Sam On Fri, Jul 1, 2022, at 1:54 PM, Michael Powe wrote: > > On 6/30/2022 23:53, Tim Cross wrote: > > Richard Stallman writes: > > > > I agree that links to liberapay might someday work without the donor's > > running nonfree software. But that is not likely to occur this year, > > and for it to occur in this decade is a long shot. > > > > So please don't put links to liberapay into GNU package web pages. > >> > >> Please explain how you can argue that position when the FSF has such a > >> link on their web page? Why is it OK for the FSF to do this to raise > >> funds, but not acceptable for projects to do the same? > > Why are there interstate highways in Hawaii? Why ask why? > > (I suspect that RMS doesn't have final say over that decision.) > > Thanks. > > mp > > -- > "Do not neglect to do good, and to share what you have." - Hebrews 13:16a > Michael Powe > Naugatuck CT USA > po...@ctpowe.net > > >
Re: Links to javascript-based websites from orgmode.org: Paypal and Github
On 6/30/2022 23:53, Tim Cross wrote: Richard Stallman writes: I agree that links to liberapay might someday work without the donor's running nonfree software. But that is not likely to occur this year, and for it to occur in this decade is a long shot. So please don't put links to liberapay into GNU package web pages. Please explain how you can argue that position when the FSF has such a link on their web page? Why is it OK for the FSF to do this to raise funds, but not acceptable for projects to do the same? Why are there interstate highways in Hawaii? Why ask why? (I suspect that RMS doesn't have final say over that decision.) Thanks. mp -- "Do not neglect to do good, and to share what you have." - Hebrews 13:16a Michael Powe Naugatuck CT USA po...@ctpowe.net
Re: Proposal: 'executable' org-capture-templates
On 01/07/2022 06:30, Arthur Miller wrote:
Max Nikulin writes:
(load (expand-file-name "org-multimenu"))
(org-menu-multiinstance-stateful
`((("1" "one" 1)
("2" "two" 2)))
:state (format-time-string "%T")
:text "Some heading"
:buffer-name "*Test menu*"
:handler (lambda (entry state)
(org-select-quit) ; it does not kill the buffer
(message "handler %S %S" entry state)))
I might be missunderstanding you now, but from this example it seems to me that
you see menu entries as something that aims for the menu itself, while state is
some user data?
I am feeling myself confused now. It seems you have got the idea mostly
right, but I suspect some resistance though.
For org-capture there are menu entries data in `org-capture-templates'
that is the same set of rules (how to expand templates where to store
result) for all instances of menu. I do not see any point to make each
entry an executable closure.
State specific to each menu instance consists from the following parts:
- requested action (prefix argument: goto target location, insert at point)
- data required to expand template when it is selected, namely
`org-overriding-default-time', `org-capture-initial' and maybe something
else.
Template properties and capture data are quite orthogonal and for me it
is rather natural to keep them independently. I would prefer to have
support of state at low level, but it can be added on the top of basic
functions through a closure. In a different use case, when menu is just
a collection of independent actions, there is no point in the state
shared by all entries of the menu instance.
However I would expect that menu handler is not aware if menu is implemented
using buffers. From my point of view handler should not have buffer argument.
I understand, and I agree it is not very beautiful design :). The problem is
when
client code provides its own handler. In the beginning I used a flag,
org-select-transient, to signal the menu should go away, but that wasn't very
clean either.
There are two types of actionable menu entries:
1. Ones that modify the state associated with menu instance without real
action. Currently they are e.g. toggles like body only or complete
document with headers for the export dispatcher. Menu should be retained
when such action is called.
2. Entries that call real action. In the case of export dispatcher or
`org-capture' menu buffer should be destroyed before a new one to
display export result or expanded template is created or selected.
So generally it is not possible to determine in advance if menu should
be "closed" before calling its handler. It is too late to close menu
when the handler returns some value. I considered a predicate function
that accepts menu entry data and the state and returns decision if menu
should be retained. Looking into your implementation I realized that
`org-select-quit' is almost ready to be a better solution. If the
handler just changes the state then it does not call the quit function.
Actions must invoke `org-select-quit' to notify menu implementation that
the instance may (or must) be destroyed. The only problem is currently
with multi-instance menu. Buffer is not destroyed by this function.
Despite it is possible to kill the buffer since it is passed as an
argument, I would prefer to delegate this action to `org-select-quit',
so menu caller becomes completely unaware if menu implementation uses
buffers or something else.
There are may be a convenience keyword argument that adds call of
`org-select-quit' before invoking a handler. It should be handy for
simple menu with no options that can be changed before calling an action.
The buffer text is just dead text;
It is unfortunate, I hope, you will reconsider it.
E.g. "C-c C-e" ox dispatcher has some options
and
user should see current values.
Can that be implemented as a submenu (group node as in org-capture-templates)?
I suppose, it is necessary to provide some visual feedback, so it is
obvious to user that some options is changed (e.g. "C-b" for "C-c C-e"
export). It may be a kind of always visible status line, however in some
cases it is better to display option value close to its menu entry.
In a minimal variant there may be a function to set status line and menu
keeps a pair of markers, so text between them are erased and new status
is inserted when the function is called.
In the beginning I was afraid that menu instance state may become a
serious problem with implementation you proposed. Actually it appeared
to be a matter of convenience. Entry-dependent behavior (if menu should
be kept or closed) would benefit from some polishing. Presenting to the
user changes in menu state in response to their actions should be
addressed somehow.
Re: [PATCH] worg - Reflect the removal of org-mac-link.el from org-contrib
Is there any reason why you did not publish on non-GNU ELPA? Would rather publish there as well. However I am more familiar with MELPA for now. I fully intend to move to non-GNU asap though. Best, Ihor Salut -- Aimé Bertrand aime.bertr...@macowners.club
Re: Customizing org-columns-modify-value-for-display-function to shorten time-stamps in colview
On 01/07/2022 19:06, Ihor Radchenko wrote: You could instead use (if (and value (not (string-empty-p value))) ...) `org-string-nw-p' is not identical to this expression, but it likely still can be used.
Re: Customizing org-columns-modify-value-for-display-function to shorten time-stamps in colview
Mekeor Melire writes: > But it results in empty (nil, I guess) time-stamps being displayed as > the current time; and non-nil time-stamps being displayed with the > current hour and minute. What's wrong? Empty time-stamps will be literally empty: "" (that is: empty string). (if "" 1 2) will return 1. That's why you got unexpected result. You could instead use (if (and value (not (string-empty-p value))) ...) Best, Ihor
Re: using org from git
Hello Ihor, Ihor Radchenko writes: > Roger Mason writes: > >> File is missing: Cannot open load file, No such file or directory, org > > So, your elpa.el config file is loading helm-org-rifle, which loads org > before you set load-path to the new version of Org. You need to put > load-path setting somewhere before loading anything else. Bingo! Fixed. Many thanks, Roger
Re: [BUG] random org-mode warning [9.5.4 (9.5.4-g7c61a3 @ /home/cro/.emacs.default/straight/build/org/)]
Thank you very much Ihor! I pulled from latest org immediately when you said and I can confirm I didn't see the warning anymore. Thank you for the quick fix, you're awesome! On 6/29/22 03:10, Ihor Radchenko wrote: Cristi Constantin writes: Than you for the response! I tried the fix you suggested, but I still see this: I just pushed a commit that should hopefully fix this problem. Please update Org and let me know if you keep seeing the warning. Best, Ihor
Re: Change both width and height of R plot in SRC block
Hello Gerado, Thanks for your email. I'm glad you reached out to the community. >>> Gerardo Moro writes: >>> >>> > I have been trying for over a year to change the output plot > >>> size when >>> > using Orgmode SRC blocks with R. I have tried both using > >>> orgmode settings >>> > and R settings. I feel your pain and frustration here. In the future, please reach out to the mailing list sooner. We think (together) therefore we R (org-mode users) ;-). > Gerardo Moro writes: > >> Oh my god, this works! I honestly tried everything but... >> Apologies. No need to apologise, but I hope reaching out to the mailing list will be in your definition of everything :-). Many thanks to Ihor and Thomas for your reactivity. Best regards, Jeremie
Re: Convert a Lisp expression to a tree diagram
Ihor Radchenko writes: > This capture template is public: https://github.com/yantar92/org-capture-ref Thank you! It is very complete, and I have seen that it also integrates with qutebrowser. I'll try it as soon as I have time. Best regards, Juan Manuel
Re: using org from git
Roger Mason writes:
> File is missing: Cannot open load file, No such file or directory, org
>
> This is the backtrace from emacs --debug-init:
>
> Debugger entered--Lisp error: (file-missing "Cannot open load file" "No such
> file or directory" "org")
> require(org)
>
> byte-code("\300\301!\210\300\302!\210\300\303!\210\300\304!\210\300\305!\210\300\306!\207"
> [require cl-lib dash f helm org s] 2)
> require(helm-org-rifle)
> ...
>
> load-with-code-conversion("/home/rmason/.emacs.d/ModularConfigFiles/elpa.el"
> "/home/rmason/.emacs.d/ModularConfigFiles/elpa.el" nil nil)
So, your elpa.el config file is loading helm-org-rifle, which loads org
before you set load-path to the new version of Org. You need to put
load-path setting somewhere before loading anything else.
Best,
Ihor
using org from git
Hello,
I indvertently issued 'rm -rf *' in my home directory an lost some files
a couple of days ago. I was able to restore most from backup, but
something is missing (or not working) in my org setup.
I have an org-git directory in .emacs.d that reports as 'org-version:
9.5.4 (release_9.5.4-602-g381a2a.dirty)' when I issue 'gmake'. I have
this in my emacs init file (~/.emacs):
;;; Configuration Directory
(defconst ram:emacs-config-dir "~/.emacs.d/ModularConfigFiles/" "")
;; Utility to auto-load config files
;; utility function to auto-load my package configurations
(defun ram:load-config-file (filelist)
(dolist (file filelist)
(load (expand-file-name
(concat ram:emacs-config-dir file)))
(message "Loaded config file:%s" file)
))
;; load my configuration files
(ram:load-config-file '(
"elpa.el" ; Comment this if m(elpa) plays up.
"console.el"
"extra-paths.el"
"templates.el"
"org-config.el"
"org-ox-koma-config.el"
snip
In ~/.emacs.d/ModularConfigFiles/org-config.el I have, at the top:
(add-to-list 'load-path "/home/rmason/.emacs.d/org-git/lisp")
(add-to-list 'load-path "/home/rmason/.emacs.d/org-git/contrib/lisp")
When I start emacs and run 'org-version' it reports: 'Org mode version
9.4.4 (release_9.4.4 @ /home/rmason/.emacs.d/org-git/lisp/)'. Notice
that the version (9.4.4) does not match what I have in the org-git
directory. Thinking that the org that comes with emacs (27.2 in my
case) was interfering with the git version I tried moving
/usr/local/share/emacs/27.2/lisp/org out of the way. That then causes
this error at startup:
File is missing: Cannot open load file, No such file or directory, org
This is the backtrace from emacs --debug-init:
Debugger entered--Lisp error: (file-missing "Cannot open load file" "No such
file or directory" "org")
require(org)
byte-code("\300\301!\210\300\302!\210\300\303!\210\300\304!\210\300\305!\210\300\306!\207"
[require cl-lib dash f helm org s] 2)
require(helm-org-rifle)
(lambda (pkg) (if (package-installed-p pkg) nil (package-install pkg))
(require pkg))(helm-org-rifle)
mapc((lambda (pkg) (if (package-installed-p pkg) nil (package-install pkg))
(require pkg)) (auto-complete caml slime scad-mode ess helm-org-rifle
haskell-mode lua-mode wisp-mode gnuplot meson-mode yasnippet tuareg muse iedit
google-c-style geiser flymake-cursor ecb bbdb auto-complete-c-headers lsp-mode
lsp-ui yasnippet lsp-java lsp-python-ms lsp-haskell helm-lsp lsp-treemacs
dap-mode lsp-origami lsp-dart company flycheck lsp-pyright rust-mode php-mode
scala-mode dart-mode clojure-mode typescript-mode))
(let* ((pkg-list '(auto-complete caml slime scad-mode ess helm-org-rifle
haskell-mode lua-mode wisp-mode gnuplot meson-mode yasnippet tuareg muse iedit
google-c-style geiser flymake-cursor ecb bbdb auto-complete-c-headers lsp-mode
lsp-ui yasnippet lsp-java lsp-python-ms lsp-haskell helm-lsp lsp-treemacs
dap-mode lsp-origami lsp-dart company flycheck lsp-pyright rust-mode php-mode
scala-mode dart-mode clojure-mode typescript-mode))) (package-initialize)
(package-refresh-contents) (mapc #'(lambda (pkg) (if (package-installed-p pkg)
nil (package-install pkg)) (require pkg)) pkg-list) (yas-global-mode) (add-hook
'prog-mode-hook 'lsp))
eval-buffer(# nil
"/home/rmason/.emacs.d/ModularConfigFiles/elpa.el" nil t) ; Reading at buffer
position 2468
load-with-code-conversion("/home/rmason/.emacs.d/ModularConfigFiles/elpa.el"
"/home/rmason/.emacs.d/ModularConfigFiles/elpa.el" nil nil)
load("/home/rmason/.emacs.d/ModularConfigFiles/elpa.el")
(while --dolist-tail-- (setq file (car --dolist-tail--)) (load
(expand-file-name (concat ram:emacs-config-dir file))) (message "Loaded config
file:%s" file) (setq --dolist-tail-- (cdr --dolist-tail--)))
(let ((--dolist-tail-- filelist) file) (while --dolist-tail-- (setq file (car
--dolist-tail--)) (load (expand-file-name (concat ram:emacs-config-dir file)))
(message "Loaded config file:%s" file) (setq --dolist-tail-- (cdr
--dolist-tail--
ram:load-config-file(("elpa.el" "console.el" "extra-paths.el" "templates.el"
"org-config.el" "org-ox-koma-config.el" "yasnippet.el" "utilities.el"
"customisations.el" "haskell.el" "smtp.el" "kill-emacs.el" "science.el"
"browser.el" "document-systems.el" "languages.el" "mu4e.el" "lsp-mode.el"))
eval-buffer(# nil "/home/rmason/.emacs" nil t) ; Reading at
buffer position 960
load-with-code-conversion("/home/rmason/.emacs" "/home/rmason/.emacs" t t)
load("~/.emacs" noerror nomessage)
startup--load-user-init-file(#f(compiled-function () #)
#f(compiled-function () #) t)
command-line()
normal-top-level()
Sorry for the long post, any help will be much appreciated.
Thanks,
Roger
emacs 27.2 on FreeBSD 12.3
Re: [PATCH] Fix typos
Stefan Kangas writes: > Please see the attached. Thanks! Applied onto main via 41e19f1d7. Best, Ihor
Re: [PATCH] worg - Reflect the removal of org-mac-link.el from org-contrib
Aimé Bertrand writes: > New patch file attached. Thanks! Applied onto master via aeb504f6. > + It's also available in [[https://melpa.org/#/org-mac-link][MELPA]]. Is there any reason why you did not publish on non-GNU ELPA? Best, Ihor
[PATCH] oc-csl: Add support for nocite citations
Dear All, the attached patch adds support for nocite citations in the csl org-cite export processor, including support for using the special key "*" to include all entries in the bibliography. best wishes, András From 3e6514d2e2f4fa68462a02578880b126e3116739 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Andr=C3=A1s=20Simonyi?= Date: Fri, 1 Jul 2022 10:24:17 +0200 Subject: [PATCH] oc-csl.el: Add support for nocite citations * lisp/oc-csl.el (org-cite-csl--rendered-citations): Collect nocite style citations in a separate list as required by the citeproc-el API. Set the output of all nocite citations to the empty string. (org-cite-csl--nocite-p): New helper predicate for checking whether a citation is a nocite. --- etc/ORG-NEWS | 5 + lisp/oc-csl.el | 53 -- 2 files changed, 43 insertions(+), 15 deletions(-) diff --git a/etc/ORG-NEWS b/etc/ORG-NEWS index 902d70256..0f7a9e825 100644 --- a/etc/ORG-NEWS +++ b/etc/ORG-NEWS @@ -239,7 +239,12 @@ This behaviour can be changed by supplying a =:align= parameter. The tabbing environment can be useful when generating simple tables which can be span multiple pages and when table cells are allowed to overflow. +*** Support for nocite citations in the csl export processor +The csl citation export processor now supports `nocite' style +citations that add items to the printed bibliography without visible +references in the text. Using the key `*' in a nocite citation +includes all available items in the printed bibliography. ** New functions and changes in function arguments *** New function ~org-element-cache-map~ for quick mapping across Org elements diff --git a/lisp/oc-csl.el b/lisp/oc-csl.el index eb67092dd..05e4fa976 100644 --- a/lisp/oc-csl.el +++ b/lisp/oc-csl.el @@ -59,9 +59,13 @@ ;; - author (a), including bare (b), caps (c), bare-caps (bc), full (f), ;; caps-full (cf), and bare-caps-full (bcf) variants, ;; - noauthor (na), including bare (b), caps (c) and bare-caps (bc) variants, +;; - nocite (n), ;; - year (y), including a bare (b) variant, ;; - text (t). including caps (c), full (f), and caps-full (cf) variants, ;; - default style, including bare (b), caps (c) and bare-caps (bc) variants. +;; +;; Using "*" as a key in a nocite citation includes all available items in +;; the printed bibliography. ;; CSL styles recognize "locator" in citation references' suffix. For example, ;; in the citation @@ -103,6 +107,7 @@ (declare-function citeproc-create "ext:citeproc") (declare-function citeproc-citation-create "ext:citeproc") (declare-function citeproc-append-citations "ext:citeproc") +(declare-function citeproc-add-uncited "ext:citeproc") (declare-function citeproc-render-citations "ext:citeproc") (declare-function citeproc-render-bib "ext:citeproc") (declare-function citeproc-hash-itemgetter-from-any "ext:citeproc") @@ -296,6 +301,12 @@ INFO is the export state, as a property list." (citeproc-proc-style (org-cite-csl--processor info +(defun org-cite-csl--nocite-p (citation info) + "Non-nil when CITATION object's style is nocite. +INFO is the export state, as a property list." + (when-let ((style (car (org-cite-citation-style citation info +(or (string= style "nocite") (string= style "n" + (defun org-cite-csl--create-structure-params (citation info) "Return citeproc structure creation params for CITATION object. STYLE is the citation style, as a string or nil. INFO is the export state, as @@ -535,20 +546,31 @@ INFO is the export state, as a property list. Return an alist (CITATION . OUTPUT) where CITATION object has been rendered as OUTPUT using Citeproc." (or (plist-get info :cite-citeproc-rendered-citations) - (let* ((citations (org-cite-list-citations info)) - (processor (org-cite-csl--processor info)) - (structures - (mapcar (lambda (c) (org-cite-csl--create-structure c info)) - citations))) -(citeproc-append-citations structures processor) -(let* ((rendered -(citeproc-render-citations - processor - (org-cite-csl--output-format info) - (org-cite-csl--no-citelinks-p info))) - (result (seq-mapn #'cons citations rendered))) - (plist-put info :cite-citeproc-rendered-citations result) - result + (let ((citations (org-cite-list-citations info)) + (processor (org-cite-csl--processor info)) + normal-citations nocite-ids) + (dolist (citation citations) + (if (org-cite-csl--nocite-p citation info) + (setq nocite-ids (append (org-cite-get-references citation t) nocite-ids)) + (push citation normal-citations))) + (let ((structures + (mapcar (lambda (c) (org-cite-csl--create-structure c info)) + (nreverse normal-citations + (citeproc-append-citations structures processor)) + (when nocite-ids + (citeproc-add-uncited nocite-ids
