Re: Changed list indentation behavior: how to revert?

i wanted first to thank everyone for their participation in this discussion. i want to not be annoying. and, yes, this is a long thread, and for me, at least, it's hard to keep track of what was said. (like many, i assumed this was some bug, triggered by my configuration TIMES emacs release

Re: Changed list indentation behavior: how to revert?

hi, all. David Rogers wrote: > Am I crazy to say that your last example of unwanted behavior is > easier for me to read and understand? (and to me the common > indenting is a hopeless mess?) yes, in fact, the "new" way sort of has the buffer indentation match that of the outline structure of

Re: Changed list indentation behavior: how to revert?

so, i also agree that the new('ish) behavior is somewhat surprising. [i once changed the behavior of the "Enter" key in Berkeley Unix, and suffered the (well-deserved, in that case) arrows that soon entered my back.] from that perspective, i wonder if maybe there's an interpretation of

Re: Thoughts on the standardization of Org

Jean Louis, > Like alias cat='sequence off; cat' something like that > > Somebody already mentioned there is cat -v to show nonprinting > characters with notation ^- and M- so that may be the solution and I > may be wrong there. yes, 'cat -v' will do it for you. (or, i'd like to know if i've

Re: Thoughts on the standardization of Org

Maxim, thanks. small note. > The sour story is that it is unsafe to feed non-trusted files directly > to terminal. A filter against control sequences is required. thus, the '-v' argument to cat(1) (which Rob Pike famously considered harmful. :) cheers.

Re: Thoughts on the standardization of Org

:)

Re: Thoughts on the standardization of Org

Tim, > No email can be considered 100% safe. "e-mail doesn't kill people; e-mail readers kill people". i would guess using 'cat -v' to read e-mail is 100% safe. even throwing in uudecode(1), or whatever is needed to decode base64, (and then piping through 'cat -v', of course ), it's probably

Re: Thoughts on the standardization of Org

Eric, > For instance, in my recent org documents, I have added a #+calc: keyword > which I use for embedded calc lines. This allows me to have a clearly > labelled line that Calc will recognise and that I can process using a > filter before export while also ensuring that other tools, e.g. ones

Re: Thoughts on the standardization of Org

Eric, i was thinking of replying to your earlier post on the power of emacs. now i guess i'll ask my question or make my vague point or whatever. i wonder if it's possible (ignoring the possible utiltiy) to divide org mode into two (maybe three?) things. first is "org mode as a document

Re: Viewing link information

Russell, > Are there other ways to view information about an org link that I > don't list below? i'll admit, this is how i do it: position cursor just before link, right arrow, C-d: having deleted the initial '[', the rest is revealed. then, C-_ to undo.

Re: best practices query: non-emacs packages based on tangled source

Immanuel, my take > - Not possible to tangle all code going to a specified file i'm not sure what this means. > - Not possible to add line directives without major surgery yes, that would be a problem (... if i were programming in, e.g., C, etc., so *is* for other people). > - Not all

Re: best practices query: non-emacs packages based on tangled source

Tom, thanks very much for your very detailed analysis and explanation of the issues you've had. it's taken me this long to read through it carefully. the issues with python source blocks [C-c C-c] versus [C-c C-v C-t] are in fact unfortunate, as it does make it hard to develop without lots of

best practices query: non-emacs packages based on tangled source

hi. i apologize if this has been asked before (especially if by me). but, since i had a question recently about Org Src... buffers, this came up. i'm wondering what people do who want to release a non-emacs'y package (an R package, say, or ...), and who did their development "from within" a .org

Re: buffer name of Org Src...

Eric, > But that's what git etc. are for! ;-) yes, but. the first time i 'C-c C-v t' in the base file onto a changed-but-uncommitted tangled file, even git will provide me no succor. cheers, Greg

Re: buffer name of Org Src...

Eric, thanks. de-tangling sounds like a possible solution. though, at least with Org Src ... buffers, org/emacs mostly keep me from messing up by, e.g., making changes in both the base file source block and in the Org Src... buffer (which i assume the de-tangling solution can't?). given my

Re: buffer name of Org Src...

Arne, no, sorry, i don't use either flymake or flycheck. cheers, Greg

buffer name of Org Src...

hi, all. i often write my version of (il)literate programs using one .org file, from which four or five (typically) files are tangled. and, generally, i'm very happy with this. but, when i have multiple Org Src ... buffers open, all from the same language, i am at a loss on how to determine to

Re: Bug: lisp error on user error [9.3.6 (9.3.6-43-gc77edd-elpa @ /home/minshall/.emacs.d/elpa/org-20200413/)]

Bastien, > thanks for reporting this. I've pushed a quick fix in master so that > it now displays an error as the output and does not choke at the user > as it did before. thank you!

Re: [PATCH] ob-core: Display warning on failure to read results

Kyle, thanks for the reply and for the patch. cheers, Greg

Bug: Code block returned no value [9.1.9 (release_9.1.9-65-g5e4542 @ /usr/share/emacs/26.3/lisp/org/)]

hi. i'm running R code from an org mode file. i was having a problem where a code block that *was* returning a value result was not returning the results into the buffer. (after long head-scratching) this appears to be because my code was returning more lines of results than

Bug: lisp error on user error [9.3.6 (9.3.6-43-gc77edd-elpa @ /home/minshall/.emacs.d/elpa/org-20200413/)]

hi. the following example should possibly result in an error message, but actually causes a lisp error/backtrace. i have a code block with ":results vertatim :colnames yes", and am returning a simple character string (so, no headers -- tsk, tsk, a user error). this happens with 'emacs -Q'. if

Re: babel/noweb concatenation of equally-named code blocks fails?

Nicolas, below is a format-patch. i signed FSF papers for emacs a number of years ago (and for gawk more recently). cheers, Greg From e2d440186ccf62216406abb440455edbac72ba79 Mon Sep 17 00:00:00 2001 From: Greg Minshall Date: Wed, 22 Apr 2020 14:45:52 -0700 Subject: [PATCH] some clarification

Re: babel/noweb concatenation of equally-named code blocks fails?

hi, Nicolas, thanks, and sorry, i should have git-pull'd. the new version seems very nice to me. two minor edits i might make to the first paragraph, 1) to make clear that #+name: names only one block, and 2) to (maybe?) simplify the latter part of the same paragraph, while, at the same time,

Re: babel/noweb concatenation of equally-named code blocks fails?

Nicolas, thank you. wordsmithing opens up endless possibilities, so i don't know that the following is at all an improvement on your suggestion. but, it occurs to me to get the importance of =noweb-ref=, and its role in concatenation, brought out early on the "page". one paragraph currently

Re: babel/noweb concatenation of equally-named code blocks fails?

Nicolas, thanks for the history! sounds like a good tradeoff. i agree, a bit more documentation would be good. cheers, Greg

Re: babel/noweb concatenation of equally-named code blocks fails?

Nicolas, thanks. i take it this is a change from (recent?) past behavior? it was kind of nice the old way, but i suspect i'll get used to the new way (no names, just noweb-ref) fairly soon. cheers, Greg

babel/noweb concatenation of equally-named code blocks fails?

hi. the description of :noweb-ref says When expanding “noweb” style references, the bodies of all code block with _either_ a block name matching the reference name _or_ a ‘:noweb-ref’ header argument matching the reference name will be concatenated together to form the replacement text.

Re: Bug: error: (invalid-function org-table-with-shrunk-field) [9.2.6 (9.2.6-4-ge30905-elpaplus @ /home/minshall/.emacs.d/elpa/org-plus-contrib-20191014/)]

Nicholas, thanks for trying. i am also unable to reproduce it. i notice there appears to be a new org-plus-contrib, and i suppose that might be a factor. (or, i messed up somehow.) presumably, this is a dead bug. in case it's *not* dead: i notice in my notes i had found this

[O] Bug: error: (invalid-function org-table-with-shrunk-field) [9.2.6 (9.2.6-4-ge30905-elpaplus @ /home/minshall/.emacs.d/elpa/org-plus-contrib-20191014/)]

Remember to cover the basics, that is, what you expected to happen and what in fact did happen. You don't know how to make a good report? See https://orgmode.org/manual/Feedback.html#Feedback Your bug report will be posted to the Org mailing list.

[O] (re-)introducing: orgtbl-query (nee org-query)

apologies for the extra noise. i've renamed (and moved) my small utility, now known as orgtbl-query, that allows one to query, from the shell (command line), the contents of an org-mode table in a file. orgtbl-query is now located at: https://gitlab.com/minshall/orqtbl-query part of it

Re: [O] small bash/awk script to query org-mode tables

Adam, thanks for the feedback. i hadn't known about org-ql -- very nice. i've renamed the gitlab *project* org-table-query-script, though i've kept the command, itself, the simpler org-query. does that seem reasonable? if so, i'll do whatever i need to give the gitlab URL for my project "that

[O] small bash/awk script to query org-mode tables

hi, all. for a project, i wanted to be able to easily query the contents of a table in an org-mode document from the shell. in case that it might be useful to others, the result is: https://gitlab.com/minshall/org-query the beginning of the help output is: usage: org-query

[O] Bug: (R?) colnames sometimes appear, sometimes don't [9.1.13 (release_9.1.13 @ /usr/local/share/emacs/site-lisp/org/)]

Remember to cover the basics, that is, what you expected to happen and what in fact did happen. You don't know how to make a good report? See https://orgmode.org/manual/Feedback.html#Feedback Your bug report will be posted to the Org mailing list.

Re: [O] non-space, paste, (???) character for inline results

> Hmmm, you may well be right. Fair enough. I reverted it. thanks!

Re: [O] non-space, paste, (???) character for inline results

> Of course we do: just write > > foocall_foo() > > or > > foocall_foo() !!! :) (but, seems less intuitive. maybe my math/CS brainwashing, liking to have lexical elements, etc.; that part of me would still vote for reverting.)

Re: [O] non-space, paste, (???) character for inline results

Nico, thanks for the reply. i'd suggest reverting (most of) 7efa... so that foocall_foo() *stays* as foocall_foo(). (i.e., put the "\\<" back in front of "call_" and "sys_".) otherwise, we have no (straight forward) way (am i right? sometimes my head hurts!) to get a plain "foocall_foo()" in

Re: [O] non-space, paste, (???) character for inline results

e prefixes CALL_FOO() with *two* ZWSPs. >From df94d943d085947212d96eddec9870d7dca0ea23 Mon Sep 17 00:00:00 2001 From: Greg Minshall <minsh...@acm.org> Date: Thu, 1 Feb 2018 11:32:59 +0530 Subject: [PATCH] use ZERO WIDTH SPACE as a separator for call_, src_ (but, don't leave around i

Re: [O] non-space, paste, (???) character for inline results

rs, Greg >From e0337aabb13fabcefbb0a9fd65e8d4c9bcd412ee Mon Sep 17 00:00:00 2001 From: Greg Minshall <minsh...@acm.org> Date: Wed, 31 Jan 2018 20:38:35 +0530 Subject: [PATCH 1/2] use '#' as a "paste" character (for call_ and src_) --- lisp/org-element.el | 10 ++ 1 file changed, 6 insertions(+),

Re: [O] non-space, paste, (???) character for inline results

ensive the latter is compared to the former.) cheers, Greg >From e0337aabb13fabcefbb0a9fd65e8d4c9bcd412ee Mon Sep 17 00:00:00 2001 From: Greg Minshall <minsh...@acm.org> Date: Wed, 31 Jan 2018 20:38:35 +0530 Subject: [PATCH] use '#' as a "paste" character (for call_ and src_)

Re: [O] non-space, paste, (???) character for inline results

Nico, ah, thanks! not wanting to look gift horses, etc., but i've a question. if i understand the change correctly - (looking-at "\\

Re: [O] non-space, paste, (???) character for inline results

Nicolas, great! except, oh, well, maybe you really meant to respond to this other set of messages, with subject line Re: [O] BUG report [Was: computing the size of a tikz to png image during export] --- cheers, Greg

[O] non-space, paste, (???) character for inline results

hi. thanks again for org-mode. having discovered this variable, i tend to run with : #+bind: org-babel-inline-result-wrap "%s" but, at the same time, i'd often like to put some character(s) before or after the result of some particular inline call, e.g., a dollar sign, a percent, etc. i could,

Re: [O] Proposal and RFC for improving ob-python

hi, John, > I like the idea behind ob-ipython, hopefully where it might go as > ob-jupyter, which could make it able to run many other languages via > the jupyter project and it's kernels. thanks for the reply. i'm not really up to speed on Jupyter, et al. but, from a brief look, my work is

Re: [O] Proposal and RFC for improving ob-python

progress, either by Ondřej or anyone else? if my frustration level remains high enough, i might try to see if i can do anything. cheers, Greg Minshall

Re: [O] org-info.js not displaying document?

i was expecting. given that i'm running off the git version, and maybe things are changing under me, i'm not sure if i should try to track this down any more. but, if i should, i'm happy to debug further. thoughts? cheers, Greg Minshall

Re: [O] org-info.js not displaying document?

oof. my problem does *not* happen with "emacs -Q". sorry about not checking that before complaining. (if anyone has any hints...) Greg Minshall <minsh...@acm.org> wrote: > hi. i'm trying to export a file using org-info.js, but i'm not getting > anything (other t

[O] org-info.js not displaying document?

y thoughts? if i didn't see the error message, i'd be sure i was doing something wrong (but, possibly i still am). cheers, Greg Minshall ps -- here is a trivial file that fails for me: * testing #+INFOJS_OPT: view:showall toc:2 this is a test ** here is something ** here is something else with

[O] org-mode and/versus make/makefiles

, for similar reasons. then, if i have one calling the other calling the first... i'm wondering if anyone else, having wrestled with these issues, has any recipes for some approximation of happiness. or, some totally different approach i'm too set in my ways to see. cheers, Greg Minshall

Re: [O] a minor patch to awk invocation

thanks -- nice!

Re: [O] a minor patch to awk invocation

very nice -- thanks! I've just pushed up a patch which changes the behavior of awk code blocks to assign variables on the command line, so the following now work. #+begin_src awk :var a=2 BEGIN{ print a; } #+end_src #+RESULTS: : 2

Re: [O] a minor patch to awk invocation

though, in the spirit of no good deed goes unpunished: #+name: foo | a | b | c | #+begin_src awk :var a=foo BEGIN{ print a; } #+end_src gives an error (and, ':var a=this is a test' doesn't behave as one might expect). i haven't looked at ob-*.el enough to know the patterns used to wrap

[O] exporting link abbreviations

active in my org-mode buffer itself (something i find so magical, plus it helps entering the info to be able to check the map before exporting). i wonder if there's something i've missed? or, if something could be added? cheers, Greg Minshall

Re: [O] exporting link abbreviations

Nicholas, You may want to add gmap as a new link type with dedicated export functions. See `org-add-link-type'. awesome -- thanks! (sorry i didn't see it/think of it in the manual.) cheers, Greg Nicolas Goaziou n.goaz...@gmail.com wrote: Hello, Greg Minshall minsh...@acm.org writes

Re: [O] [PATCH] Use geiser for babel scheme evaluation.

hi, Eric, this patch isn't mine, but rather Michael Gauland's; i just wondered where it had gone. cheers, Greg here is the thread: http://comments.gmane.org/gmane.emacs.orgmode/64229

Re: [O] [PATCH] Use geiser for babel scheme evaluation.

hi, Bastien, hi. what happened to this patch? i don't see it anywhere. cheers! Can you give a pointer to this patch? here is the thread: http://comments.gmane.org/gmane.emacs.orgmode/64229 cheers, Greg

Re: [O] [PATCH] Use geiser for babel scheme evaluation.

hi. what happened to this patch? i don't see it anywhere. cheers!

Re: [O] MobileOrg for iOS approved and soon to be available in the app store

For those interested in MobileOrg on iOS devices, it has been approved and will be back in the store soon, it can take up to 24 hours to become available. awesome!! thanks *very* much!!

Re: [O] selecting columns to export

Sebastien, Put a partial echo code block (one where you select in the var header argument which columns interest you), and output the results of that code block? thanks! below is the final result of your suggestion. (my table was long, so i had to use longtable; i also used a landscape

[O] spreadsheet hline-relative (I) field references

hi. i've two suggestions/requests/queries about using hline-relative references, e.g., @III, in formulas in org-mode spreadsheets. 1. i would like to use this syntax on the *left* hand side of a formula. e.g., #+TBLFM: @I$2=vsum(@-I$1..@+I$1) (meaning, the second column in the first

Re: [O] parameterizing keyword values during a #+call

Gary, Org-mode macros that got expanded in the middle of babel source block text would be cool. Just saying. i agree with Eric's comment. if you think of the issue of trying to parse an arbitrary (and growing) number of languages, trying to avoid language-specific constructions in your choice

[O] selecting columns to export

hi. i have an org-mode table with a large number of columns, but would like to export only a small number of them. is there an obvious way of doing this? cheers, Greg

[O] odd behavior for begin_src org :results

Org-mode version 8.0.1 (release_8.0.1-42-g267cbe @ /Users/minshall/usr/share/emacs/site-lisp/org/) hi. the following produces #+RESULTS: #+begin_src org :results replace hello #+end_src but, repeated evaluations seem to grow the list of results. e.g., after four evaluations:

Re: [O] odd behavior for begin_src org :results

Eric, thanks for the answer. another #+begin_src org question. it appears that only *string* values are allowed for any :var that are defined (i.e., ':var bar=foo', and *not* ':var bar=3'). since i'm not 100% sure of the semantics, maybe this is desired. if one *should* be allowed to pass in,

Re: [O] parameterizing keyword values during a #+call

Eric, just for completeness, and in case this may be of use to other people, below is the result of my question + your suggestions. the following illustrates org-mode plus asymptote producing a .svg file during html export, and a pdf file during any other (presumably, latex) export. thanks

Re: [O] runaway argument exporting: * _is_?

Nicolas, Isn't it a LaTeX limitation? What would the correct LaTeX code be in that case? this seems to be something in beamer rather than inside vanilla latex. for example, the following foo.tex file fails: \documentclass{beamer} \begin{document} \section{\underline{is}?} \end{document}

Re: [O] variable names in manual

hi, Bastien, IMHO this rather call for making C-h v (and C-h f) case-non-sensitive. yes, except elisp variables are *not* case sensitive. so, if fu-bar and FOO-BAR are different variables, would C-h v put up (some sort of) a dialog to choose between them? it would be slightly messy. cheers,

Re: [O] parameterizing keyword values during a #+call

Eric, thanks! Something like the following should work. #+call: disc[:file (if (and (boundp org-export-current-backend) (equal org-export-current-backend 'html)) foo.svg foo.tex)]() :results file in fact, with the new exporter, org-export-current-backend has bit the dust, but apparently

Re: [O] variable names in manual

yes, except elisp variables are *not* case sensitive. You mean... they *are* case-sensitive, right? indeed! insert-sheepish-smiley. Mh.. if fu-bar and FU-BAR are two different variables, I guess we should rename one of name anyway. Hence my initial proposal :) i agree -- having two

Re: [O] parameterizing keyword values during a #+call

Eric, And you could wrap up the extra-long Emacs-lisp in a function or macro in your init to avoid the overlength header argument. is it possible to embed the function inside the .org file itself? (in order to promote sharing of .org files, without needing any more-than-necessary ancillary

Re: [O] parameterizing keyword values during a #+call

Eric, You could put the emacs-lisp code into an emacs-lisp code block which is exported but has a result type of none or silent. ah -- i should have tried that! that works -- thanks *very* much! cheers, Greg

[O] runaway argument exporting: * _is_?

-minshalls-mbp: {1039} diff sectbug.texH:1 sectbug.texH:2 38,39c38,39 \begin{frame}[label=sec-1]{\underline{is}?} \end{frame} --- \section[\underline{is}?]{\underline{is}?} \label{sec-1} am i doing something wrong? (this is fallout converting from 7.9.3f to 8.) cheers, Greg Minshall

[O] variable names in manual

hi. the info pages seem to have convert

[O] variable names in manual

clear what is, and what isn't, a variable name. but, it means that placing the cursor over the name and hitting C-h v doesn't default to that name. (and, i've always found that a convenient way to navigate.) so, just curious is it might make sense to revert to lower case names. cheers, Greg Minshall

[O] parameterizing keyword values during a #+call

appreciation of what a pain macros are to implement fully, halfly, anyly), Greg Minshall (*) #+MACRO: ext @@latex:pdfbeamer:pdfhtml:svg@@

Re: [O] edit-src on read-only files

it seems like org-mode should prevent that. Yes, this is now the case in master. Thanks! great -- thank you!!

[O] edit-src on read-only files

hi. i use RCS on my .org files. it's happened to me more than once (1 == shame on me) that i've entered C-c ' on a read-only .org file, spent some time editing the source code fragment, then done C-c ', only to lose my edits, as the original buffer was read-only. it seems like org-mode should

Re: [O] LaTeX-export: letters after $..$ turn off math-mode

hi. this was on the list a year ago (see below). i'd like to plead the case of allowing the user to suppress dollar-sign behavior (or, force dollar-signs to mean math-mode). the main reason is convenience: when trying to quickly write up thoughts, typing $ a = b^2 $ is just that much more

Re: [O] Change: no longer automatically evaluate embedded elisp in code block output Was: babel awk with table input: Code block produced no output.

... For this reason I've just pushed up a change which does as you suggest and inhibits lisp evaluation in the `org-babel-import-elisp-from-file' function which is only used to import emacs-lisp results from code blocks. ... This will now report the error with a message, but will still return

Re: [O] babel awk with table input: Code block produced no output.

-file, which then just silently returns a nil. the second question is, should it report an error to the user? cheers, Greg Minshall hi. it appears that a left or right paren in an entry in a table makes awk not execute. here's an example (change :stdin fails to :stdin works to see it work

Re: [O] babel awk with table input: Code block produced no output.

Tom, :results output sounds right for awk as a report formatter. I'm wondering if there is a need for :results value with awk? yes, i agree. i didn't get far enough into the code to see where the value result was coming from. cheers, Greg

Re: [O] make install-info error messages

Achim, this is fink's install-info, living in /sw/bin. it covers (now that i'm looking) /usr/bin/install-info. bash greg-minshalls-mbp: {1080} /usr/bin/install-info --version install-info (GNU texinfo) 4.8 (it's odd, but not likely of interest, that fink claims i texinfo

[O] whole-adze dataset?

?), but web searches have been useless. what am i missing? cheers, Greg Minshall

<    1   2   3   4