Re: A few changes to test in master
On Wednesday, 5 Feb 2020 at 08:08, Bastien wrote: > I just fixed the scroll-bar issue, thanks! Confirmed! Many thanks. -- : Eric S Fraga via Emacs 28.0.50, Org release_9.3.2-198-g06d36e
Re: Bug: org-element-at-point on headline does not contain :parent property [9.3 (release_9.3 @ /home/yantar92/.emacs.d/straight/build/org/)]
Hi Ihor, Ihor Radchenko writes: > According to org-element-at-point docstring, "Properties depend on > element or object type, but always include :begin, :end, :parent and > :post-blank properties.". Probably the docstring needs to be adapted - Nicolas knows this area better than me. Best, -- Bastien
Re: A few changes to test in master
"Fraga, Eric" writes: > Much better. See attached screenshots. One with scroll bar (which I > normally don't have turned on) and one with line numbers (which I do > usually have). I just fixed the scroll-bar issue, thanks! -- Bastien
Re: Bug: org-map-entries infinite loop for org file with tags [9.2.6 (9.2.6-elpa @ /home/ian/.emacs.d/elpa/org-9.2.6/)]
Hi Ian, > Running org-map-entries on an org file with tags results in an infinite > loop. FWIW, I cannot reproduce this. > Example function using org-map-entries: > > (defun org-map-entries-test () > (interactive) > (org-map-entries '(lambda () (message "%s" (org-entry-properties > (point) 'standard > (message "done")) > > Example org file: > > * one > * two > * three > :noexport: The above exemple is not a valid org file, the tag should be on the same line than the headline... but perhaps that's just because your email was sent as HTML. Thanks, -- Bastien
Re: sub super script export default
On Tuesday, 4 Feb 2020 at 15:31, Samuel Wales wrote: did you export your signature? I did! And, yes, org-htmlize interpreted the underscore in the version number. Does it look better now? I don't often use HTML emails, mind you. Thank you! – Eric S Fraga via Emacs 28.0.50, Org release_9.3.2-198-g06d36e
Re: Bug: org-agenda-open-link disallow permanenly changing point position while opening some links (e.g. elisp:) [9.3 (release_9.3 @ /home/yantar92/.emacs.d/straight/build/org/)]
Hi Ihor, thanks for reporting this, this should be fixed now. -- Bastien
Re: Bug: refiling gobbles a newline and absorbs the next heading [9.1.9 (release_9.1.9-65-g5e4542 @ /Applications/Emacs.app/Contents/Resources/lisp/org/)]
Hi Miguel, I made a change in Org maint branch that could somehow impact the issue you reported. Can you test and see if it does? Morin writes: > In the course of fixing this, I found another bug in using the hook > `org-capture-before-finalize-hook`, which adds text at the beginning > and end of the org buffer and not in the beggining and end of the > capture item. If this is really another bug, please fill a different bug report for it, it helps us track all issues separately. Thanks, -- Bastien
Re: A few changes to test in master
On Wednesday, 5 Feb 2020 at 00:21, Bastien wrote: > This should be fixed now, thanks! Much better. See attached screenshots. One with scroll bar (which I normally don't have turned on) and one with line numbers (which I do usually have). >> org-table-header-line-mode: Symbol’s function definition is void: >> face-remap-remove-relative > > Mhh... this I cannot reproduce (with Emacs -Q and latest master). > Let me know if you find where lies the problem. This seems to have been fixed. Thank you. -- Eric S Fraga via Emacs 28.0.50, Org release_9.3.2-198-g06d36e
Re: Bug: wsl org-open-at-point [9.1.14 (9.1.14-9-g131531-elpa @ /home/boss5/.emacs.d/elpa/org-20181112/)]
Hi Steve, thanks for reporting this issue. Can you or Fabrice suggests what change should be done in Org, if any? Also, perhaps another solution can be found by adapting `org-file-apps'? Thanks, -- Bastien
Re: A few changes to test in master
Hi Jack, Jack Kamm writes: > Bastien writes: > >> - M-x org-table-electric-header-mode RET will display the first row >> of the table at point in the header line when the first row is not >> visible anymore. > > This is great, it's a huge quality-of-life improvement for working with > long tables. Below are some issues I noticed when playing with it. Thanks for testing and taking the trouble to report these issues. > The variable `org-table-header-line-p' doesn't seem to have any effect > for me, I find that I need to call "M-x org-table-header-line-mode" even > when it's set. Should be fixed now. > Also, "M-x org-table-header-line-mode" seems to activate the minor mode > globally, despite a message suggesting it is only activated in the > current buffer. Maybe because we use "defvar" instead of "defvar-local" > to define its variable? > > I tried replacing the "defvar" with "defvar-local", it seemed to fix the > global activation of the minor mode, but still it seems the hooks added > are still active in other org buffers. So if I activate the mode in > buffer A, then view a long table in buffer B, I see the table header > when scrolling through it, even though the mode isn't active in B. Well, I tried various things and I didn't fix this one. Perhaps this is due to the special display of the header line. I will continue to look for a solution. > If I am in a table, and scroll-up-command brings me out of the table, > then the header of the table still sits on top of the window immediately > after scrolling. This gets fixed as soon as any action is taken > (e.g. moving the cursor or hitting C-g). Yes, this happened to me sometimes. I think I enhanced the situation a bit here, but I can't tell for 100% sure. Please test and report. > It would be nice if the header row was a little more visually > distinguishable from the other table rows (maybe by adding an underline > to that row?) Good idea, done - you can now customize the face: M-x customize-face RET org-table-header RET > Feature request (for Org 9.5?): > > It would be great if an analogous feature could be added for the > left-most column of a table, so if a table is very wide, and I scroll to > the right, I could still see which row index I'm in. Yes. I am still trying to precisely see the problem and solve it in a way that's not too invasive. Best, -- Bastien
Re: How to set time limit and memory limit for execution of source blocks
Anoop GR writes: > Dear Emacs hackers, > > Like all of you, I think orgmode is the best way to organise study notes. > > I am solving competitive programming questions from Topcoder.com > There are strict guidelines on memory limit of 256MB and time limit of 2sec > for solutions > > How do I enforce the same on my orgmode source blocks. > I want the execution to stop whenever it exceeds the above limits on memory > and time. > > Long live Emacs, > Anoop Just an possible solution, use Emacs advice on org-babel-execute: to modify the language execute command. Prepend with Linux commands which can limit process resources. -- [ stardiviner ] I try to make every word tell the meaning what I want to express. Blog: https://stardiviner.github.io/ IRC(freenode): stardiviner, Matrix: stardiviner GPG: F09F650D7D674819892591401B5DF1C95AE89AC3
Re: feature request: modify org-attach to also create new (non-text) attachments
Bastien writes: > Hi Simon, > > Simon Campese writes: > >> while in orgmode, I frequently create some handwritten notes (using >> a wacom tablet and xournalpp) and attach it to the current >> headline. My ad-hoc solution is the following trivial modification of >> org-attach-new (only the second to last line has changed): > > if this is still relevant, can you send a patch against org-attach.el > from the master branch? > > See https://orgmode.org/worg/org-contribute.html on how to contribute. > > Thanks, Agreed, I like this method. I have this needs too. Hope this can be added into org-attach. Simon :) -- [ stardiviner ] I try to make every word tell the meaning what I want to express. Blog: https://stardiviner.github.io/ IRC(freenode): stardiviner, Matrix: stardiviner GPG: F09F650D7D674819892591401B5DF1C95AE89AC3
Re: org-startup-truncated default should be nil [legibility 2/6]
should not have hit send on last email. meant to disengage completely. will do so now. last email was not an invitation to converse.
Re: org-startup-truncated default should be nil [legibility 2/6]
you do not know what every user needs.
Re: Make code elements in prose unobtrusive [legibility 6/6]
On 2/4/20, Matthew Lundin wrote: > and they are best addressed through add-on themes and packages. agreed.
Re: org-startup-truncated default should be nil [legibility 2/6]
i am feeling highly uncomfortable now. On 2/4/20, Texas Cyberthal wrote: >> many users need fully maximized emacs while still having legible paragraph >> width. > > Splitting windows vertically creates narrower columns. Unlike > truncation etc, window management actually is something all noobs must > learn. > > Narrower columns can increase reading speed, to a point. But wide > columns aren't actively uncomfortable. It isn't important for noobs to > be fast; they're slow anyway. Reducing disorientation, frustration and > distraction is the priority. > > Full width is bad for detailed reading, but it's great for skimming > the document overview. Half width is 80 chars on my primary display. > The default fill column is 70. > > It's reasonable to expect users will set font size so that vertical > window split results in a comfortable paragraph width. It's > unreasonable to expect they will hit M-q constantly to refill > paragraphs. > > On Wed, Feb 5, 2020 at 7:26 AM Samuel Wales wrote: >> >> On 2/4/20, Texas Cyberthal wrote: >> > Prose should wrap at >> > window's edge >> >> many users need fully maximized emacs while still having legible >> paragraph width. > -- The Kafka Pandemic What is misopathy? https://thekafkapandemic.blogspot.com/2013/10/why-some-diseases-are-wronged.html The disease DOES progress. MANY people have died from it. And ANYBODY can get it at any time.
Re: Make code elements in prose unobtrusive [legibility 6/6]
Adam Porter writes: > There may be improvements to be made, but the defaults shouldn't be set > to match the preferences of any one user. Remember that people have > been using Org for years, and theming and faces are very personal. ;) I strongly agree. All of the changes mentioned in these legibility threads could be accomplished through theming and Elpa/Melpa packages one could recommend to new users who easier ways to add variable pitch, unobtrusive markup, etc. It would be trivial to point a new user to install them through the package manager. It would be a bad precedent to add idiosyncratic customization options to cater to personal aesthetic preferences. As Adam says, everyone's theming preferences are personal, and they are best addressed through add-on themes and packages. Matt
Re: org-startup-truncated default should be nil [legibility 2/6]
> many users need fully maximized emacs while still having legible paragraph > width. Splitting windows vertically creates narrower columns. Unlike truncation etc, window management actually is something all noobs must learn. Narrower columns can increase reading speed, to a point. But wide columns aren't actively uncomfortable. It isn't important for noobs to be fast; they're slow anyway. Reducing disorientation, frustration and distraction is the priority. Full width is bad for detailed reading, but it's great for skimming the document overview. Half width is 80 chars on my primary display. The default fill column is 70. It's reasonable to expect users will set font size so that vertical window split results in a comfortable paragraph width. It's unreasonable to expect they will hit M-q constantly to refill paragraphs. On Wed, Feb 5, 2020 at 7:26 AM Samuel Wales wrote: > > On 2/4/20, Texas Cyberthal wrote: > > Prose should wrap at > > window's edge > > many users need fully maximized emacs while still having legible > paragraph width.
Re: Prose with markup needs more line spacing [legibility 5/6]
If a noob is using Emacs for prose, he's using Org, or at least he should be. Those using other modes for prose are probably more advanced. Regardless of how it defines itself, today Emacs is primarily an IDE for programmers. So prose-friendly defaults are specific to Org. Emacs doesn't need to be noob-friendly everywhere, just noob-friendly in one location, a "starter zone". Org is what attracts non-techies to Emacs, for its personal info management features. On Wed, Feb 5, 2020 at 7:17 AM Samuel Wales wrote: > > i get some of your points in these emails. > > i'd sure like to change physical indentation in org to don't. > > and i think newcomers and advanced alike might want to have org sub > superscript be off by default. one user on this list recently > exported a signature that contained a version number that got mangled! > > === > > however, as an example of unintended consequences, line-spacing is a > fundamental thing i'd be leery of changing. > > for one thing, it's a big problem to reduce number of lines on screen. > many users use large fonts and are struggling to make use of the > number of lines available even on the largest screens. > > i think the user would have trouble noticing that it is possible to fix. > it might look like "part of the font". > > even advanced users might not know about line spacing. faces and > display stuff are pretty complex in emacs. powerful, but complex. > > add the annoyances a user who requires large fonts has to deal with already. > > on top of that the question of what to do with partial lines at end of > window -- is scrolling idempotent? or whatefer the correct math term > for "you do a and the opposite of a and you get what you had before" > is. could cuase issued before being notices. > > and that's before differences of opinion on aesthetics. :) > > === > > but scoping out to your campaign in general, i wonder why some of your > proposals are for org. some things might be good for text mode in > general. or outline mode. or fundamental mode. if we make them only > for org, they might be nih-ish or inconsistent. > > emacs users can get curmudgeonly. don't let that stop you. but > please remember to try to falsify your hypotheses.
Re: [BUG] Infinite loop in org-agenda-show-new-time
Hi Andrew, thanks again. Andrew Hyatt writes: > Removing the (beginning-of-line 1) at the end of the time display > code in that function, and substituting (org-agenda-previous-line) > seems to fix it. I'm not sure if that's the right approach - the > previous code didn't use that function for a reason, but I don't know > what that reason was. I think this approach is correct is it will move over visible lines. I've pushed a patch, please let me know if it is fixed. Best, -- Bastien
Re: babel latex headers and image generation commands
I've thought about this more and the solution I presented above isn't quite sufficient for me. I need something where I get complete control over what goes in the latex source block on a block-by-block basis. In other words, I don't want a user-configurable option like org-format-latex-header plus a list of user-configurable packages in every block. I could add an option alongside the option I introduced above that tells the execute function to only compose the tex file from the body (btw, this doesn't have to be manual for the user, just define a class and use snippets), but at some point I wonder how much it makes sense to keep adding options to this function since it'll just make it harder to maintain. What do people think? If there's any interest, I'm more than happy to put in the extra time and add this functionality to latex-execute. Otherwise, I'll just advise the function for my own specific needs. I do think there's a real use-case here: namely, complete case-by-case control over the source latex and its output, including export backend dependent things like colors. But, maybe this is just me and the existing functionality is fine with people. Matt
Re: Weird face behavior with org-hide-emphasis-markers enabled
> Can you provide an emacs and org version, the value of the variables > at stake and an reproducible example? Hi, naturally, I just wasn't at all sure I just overlooked something obvious and it's actually common knowledge. Naturally, using emacs -Q GNU Emacs 26.3 (build 1, x86_64-redhat-linux-gnu, GTK+ Version 3.24.13) of 2019-12-10 Org mode version 9.1.9 (release_9.1.9-65-g5e4542) minimal setup: (setq org-hide-emphasis-markers t) (set-face-attribute 'org-code nil :box '(:line-width 1)) an example file mwe.org: ~sample text~ This reproduces the issue reliably. Cheers, D.
Re: org-startup-truncated default should be nil [legibility 2/6]
On 2/4/20, Texas Cyberthal wrote: > Prose should wrap at > window's edge many users need fully maximized emacs while still having legible paragraph width.
Re: Weird face behavior with org-hide-emphasis-markers enabled
Hi, D writes: > org-hide-emphasis-markers has a > strange interaction with faces like org-code: when trying to draw a box > around an emphasized expression it does not draw the right border. Can you provide an emacs and org version, the value of the variables at stake and an reproducible example? Thanks, -- Bastien
Re: A few changes to test in master
Hi Eric, "Fraga, Eric" writes: > the latest on the table header. With emacs -Q and org from a few > minutes ago, I get the following: > > screendu > > when I open the file, invoke M-x org-table-header-line-mode RET and > scroll down in the attached org file. This should be fixed now, thanks! > Note also that if I invoke the above command before opening an org > file, org complains (correctly) about the command not being suitable > outside org but then, when I open the attached file and invoke the > command again, I get: > > org-table-header-line-mode: Symbol’s function definition is void: > face-remap-remove-relative Mhh... this I cannot reproduce (with Emacs -Q and latest master). Let me know if you find where lies the problem. Best, -- Bastien
Re: Prose with markup needs more line spacing [legibility 5/6]
i get some of your points in these emails. i'd sure like to change physical indentation in org to don't. and i think newcomers and advanced alike might want to have org sub superscript be off by default. one user on this list recently exported a signature that contained a version number that got mangled! === however, as an example of unintended consequences, line-spacing is a fundamental thing i'd be leery of changing. for one thing, it's a big problem to reduce number of lines on screen. many users use large fonts and are struggling to make use of the number of lines available even on the largest screens. i think the user would have trouble noticing that it is possible to fix. it might look like "part of the font". even advanced users might not know about line spacing. faces and display stuff are pretty complex in emacs. powerful, but complex. add the annoyances a user who requires large fonts has to deal with already. on top of that the question of what to do with partial lines at end of window -- is scrolling idempotent? or whatefer the correct math term for "you do a and the opposite of a and you get what you had before" is. could cuase issued before being notices. and that's before differences of opinion on aesthetics. :) === but scoping out to your campaign in general, i wonder why some of your proposals are for org. some things might be good for text mode in general. or outline mode. or fundamental mode. if we make them only for org, they might be nih-ish or inconsistent. emacs users can get curmudgeonly. don't let that stop you. but please remember to try to falsify your hypotheses.
Re: Emacs master, faces with :extend t let cursor vanish at EOL?!
Hi Ingo, Ingo Lohmar writes: > I am confused, I thought this was fixed, but I have a really hard to find > the bug.. > > Some time later: https://debbugs.gnu.org/cgi/bugreport.cgi?bug=38330 Yes, it is fixed, I couldn't find the reference for this bug. -- Bastien
sub super script export default
did you export your signature? take a look at the version number. i'm thinking /this/ could be a default change if so :). On 2/3/20, Fraga, Eric wrote: > PS -signature out of date in this case. org up to date from 5 minutes > ago now. > – > Eric S Fraga via Emacs 28.0.50, Org release9.3.2-198-g06d36e > -- The Kafka Pandemic What is misopathy? https://thekafkapandemic.blogspot.com/2013/10/why-some-diseases-are-wronged.html The disease DOES progress. MANY people have died from it. And ANYBODY can get it at any time.
Weird face behavior with org-hide-emphasis-markers enabled
Hi all, maybe I overlooked something in the archives, but I can't find this issue having been brought up yet. org-hide-emphasis-markers has a strange interaction with faces like org-code: when trying to draw a box around an emphasized expression it does not draw the right border. Cheers, D.
Re: Prose with markup needs more line spacing [legibility 5/6]
If someone is using optional packages that add markup such as underlining to code, and the markup is so prevalent that he needs extra line spacing, he is advanced enough to know how to adjust that. Line spacing preference is idiosyncratic, and spacing varies by face as well. I propose adding an Org customization settings to adjust Org's line spacing, so that noobs can more easily achieve legibility. Adding a function that hooks to Org is too complicated.
Re: org-adapt-indentation default should be nil [legibility 3/6]
> the default settings do not put blank lines between headings and their entry > text, I don't know what this means. Plain Emacs behaves the same way Spacemacs does in this regard. Insertion of a blank line after a heading is voluntary but standrd. Insertion of a blank line between the current non-empty line and a new heading is automatic. The fact that the latter looks nice tends to make users do the former. > without any indentation, headings and entry text on varying levels tends to > blend together, making for very poor readability. If the goal is to read the body text of headings, then deeply indenting it is contrary to the goal. If the goal is to see the depth of headings, then the bodies should be folded. If folded mode doesn't convey sufficient information, the solution is to rewrite the heading titles to better summarize the body text. I never use org-adapt-indentation and have no readability issues. Out of curiosity, I tried to turn it on just now. There's no toggle for it, even though it's a buffer-local variable. This suggests it's not useful, since apparently nobody who's turned it off cares to turn it on again. > No one is "good at" Emacs and Org when they first come to it. UI difficulty is exponential, not linear. The more initially difficult the Emacs UI is acknowledged to be, the more important it is to reduce that difficulty with noob-friendly defaults, so that they can eventually reach the point of elitist unconcern for noobs. The problem with aiming software at noobs is ruining the expert experience. Changing defaults doesn't ruin expert experience because experts have configuration management. Noob friendly defaults increases the likelihood there is a long term for them. Emacs' biggest barrier to adoption is acclimatization. I just read a GTD thread in which they all agreed Org was too hard to be worth learning, including the guy advocating it: https://forum.gettingthingsdone.com/threads/emacs-org-mode-is-the-perfect-tool-for-gtd.15028/page-2 To be clear, this is the biggest GTD forum, which Org is the best implementation of, and it seems most of them are using digital GTD tools.
Re: org-startup-truncated default should be nil [legibility 2/6]
> visual-line-mode and toggle-truncate-lines are basic Emacs commands that all > users should learn early. Visual lines, logical lines etc is a complicated mess that Spacemacs avoids entirely. I recall fiddling with it and never being satisfied, until adopting Spacemacs solved it. Now I know even less about it than I did then, because there's no need to know. A brief investigation shows Spacemacs sets (line-move-visual t) in prosey text modes, so that C-n next-line operates on visual lines. However commands such as C-e operate on logical lines: mwim-end-of-line-or-code. This is a sane default that permits fluid navigation of paragraphs, which is all a noob wants to do. Similarly, I almost never use truncate-lines, to the point that I had to websearch to recall what it was called within the last week. Emacs is self-documenting; learning it requires bootstrapping. The less noob-friendly the defaults, the lower the chances they successfully boostrap. Emacs noobs have enough to contend with. If learning the twenty ways to wrap lines can be skipped, it should be. Prose should wrap at window's edge; code should continue. That's the universal standard now. Emacs was written before this standard, so it pretends there isn't one.
Re: babel latex headers and image generation commands
Ok, here's an implementation that seems to be working pretty well so
far.
`org-latex-img-process` is the new customization. Most of the execute
function is unaltered, but I've added the condition:
```
((and (not imagemagick)
(assoc extension org-latex-img-process))
```
Here's the change in full.
```
(setq org-latex-pdf-process
'("latexmk -f -interaction=nonstopmode -output-directory=%o %f"))
(setq org-latex-img-process
'(("svg" . ("dvisvgm %f -P -n -b min -o %O"
(defun org-babel-execute:latex (body params)
"Execute a block of Latex code with Babel.
This function is called by `org-babel-execute-src-block'."
(setq body (org-babel-expand-body:latex body params))
(if (cdr (assq :file params))
(let* ((out-file (cdr (assq :file params)))
(extension (file-name-extension out-file))
(tex-file (org-babel-temp-file "latex-" ".tex"))
(border (cdr (assq :border params)))
(imagemagick (cdr (assq :imagemagick params)))
(im-in-options (cdr (assq :iminoptions params)))
(im-out-options (cdr (assq :imoutoptions params)))
(fit (or (cdr (assq :fit params)) border))
(height (and fit (cdr (assq :pdfheight params
(width (and fit (cdr (assq :pdfwidth params
(headers (cdr (assq :headers params)))
(in-buffer (not (string= "no" (cdr (assq :buffer params)
(org-latex-packages-alist
(append (cdr (assq :packages params))
org-latex-packages-alist)))
(cond
((and (string-suffix-p ".png" out-file) (not imagemagick))
(org-create-formula-image
body out-file org-format-latex-options in-buffer))
((string-suffix-p ".tikz" out-file)
(when (file-exists-p out-file) (delete-file out-file))
(with-temp-file out-file
(insert body)))
((and (not imagemagick)
(assoc extension org-latex-img-process))
(with-temp-file tex-file
(insert (concat
(org-latex-make-preamble
(org-export-get-environment (org-export-get-backend
'latex))
org-format-latex-header
'snippet)
(if headers
(concat "\n"
(if (listp headers)
(mapconcat #'identity headers "\n")
headers) "\n")
"")
"\\begin{document}"
body
"\\end{document}")))
(let ((tmp-pdf (org-babel-latex-tex-to-pdf tex-file)))
(when (file-exists-p out-file) (delete-file out-file))
(let* ((log-buf (get-buffer-create "*Org Babel LaTeX Output*"))
(err-msg "fix")
(img-out (org-compile-file
tmp-pdf
(cdr (assoc "svg" org-latex-img-process))
extension err-msg log-buf)))
(shell-command (format "mv %s %s" img-out out-file)
((and (or (string= "svg" extension)
(string= "html" extension))
(executable-find org-babel-latex-htlatex))
;; TODO: this is a very different way of generating the
;; frame latex document than in the pdf case. Ideally, both
;; would be unified. This would prevent bugs creeping in
;; such as the one fixed on Aug 16 2014 whereby :headers was
;; not included in the SVG/HTML case.
(with-temp-file tex-file
(insert (concat
"\\documentclass[preview]{standalone}
\\def\\pgfsysdriver{pgfsys-tex4ht.def}
"
(mapconcat (lambda (pkg)
(concat "\\usepackage" pkg))
org-babel-latex-htlatex-packages
"\n")
(if headers
(concat "\n"
(if (listp headers)
(mapconcat #'identity headers "\n")
headers) "\n")
"")
"\\begin{document}"
body
"\\end{document}")))
(when (file-exists-p out-file) (delete-file out-file))
(let ((default-directory (file-name-directory tex-file)))
(shell-command (format "%s %s" org-babel-latex-htlatex
tex-file)))
Re: Defaults for noobs, dotfiles for vets [legibility 1/6]
Making a vet change a default if he decides he doesn't like a change upon upgrading won't drive him away, but Emacs' unfriendly defaults are always driving away noobs. Therefore Org's defaults should be noob-friendly, not vet-friendly. Probably vets should use legible settings as well. I became accustomed to less-legible Org settings, and thought they were superior. But when I cleaned up my Spacemacs config, I incidentally restored some default legibility tweaks I'd disabled. After a brief exposure, I realized the tweaks were superior, and that my preferences had been wrong. Changing the defaults can overcome vet inertia and improve their UI. > Terminals can display colors, underlines, italics, and bold text Proposed legibility changes don't affect those font aspects.
Re: Glacial file operation!
Bastien writes: > Hi Sharon, > > Sharon Kimble writes: > >> So how can I either remove it, or negate its showing its effects in >> every org-mode file please? > > Can you use `org-mode-hook' to deactivate whatever is getting in your way? Thanks for replying. I actually solved it after I'd emailed you ... I had a file containing 50+ org-mode links to various files, documents, and shell scripts. Once I'd dumped it out of emacs, everything suddenly worked as normal! My final thoughts on it is that wc-mode was trying to count the number of words and stuff in all of the files after following the links! Sorry Sharon. -- A taste of linux = http://www.sharons.org.uk TGmeds = http://www.tgmeds.org.uk DrugFacts = https://www.drugfacts.org.uk Debian 10.2, fluxbox 1.3.7, emacs 26.3, org 9.3.2 signature.asc Description: PGP signature
Re: Emacs master, faces with :extend t let cursor vanish at EOL?!
On Tue, Feb 04 2020 11:07 (+0100), Bastien wrote: > Hi Ingo, > > Ingo Lohmar writes: > >> Using this with a current elpa pkg of org-mode, and setting :extend t on >> faces like `org-block`, "often" the cursor vanishes at the EOL of a line >> using such a face. It reliably happens for `org-block', only sometimes >> for `secondary-selection'. > > can you keep track of this issue and related discussions? > > I doubt there is anything we can do in Org itself, but perhaps a hint > in a docstring could help. > > Let us know, thanks, Hi Bastien, I am confused, I thought this was fixed, but I have a really hard to find the bug.. Some time later: https://debbugs.gnu.org/cgi/bugreport.cgi?bug=38330 Best, Ingo
Re: [BUG] Infinite loop in org-agenda-show-new-time
I've tried the latest version from Feb 2nd, and it still has the same issue. After some more time with the issue, the issue is when the agenda has items A, and next line, invisibily (due to org-agenda-dim-blocked-tasks), B. Trying to set A gets you into an invisible loop because moving to the start of the line after displaying the time in org-agenda-show-new-time doesn't take you far enough back to proceed backwards. The next iteration through the loop, the time will be re-displayed. Removing the (beginning-of-line 1) at the end of the time display code in that function, and substituting (org-agenda-previous-line) seems to fix it. I'm not sure if that's the right approach - the previous code didn't use that function for a reason, but I don't know what that reason was. On Mon, Feb 3, 2020 at 2:04 PM Bastien wrote: > Hi Andrew, > > I have pushed some fixes in this area, if you have a chance to test > Org from the latest maint or master branch, please do so and report > if the problem persists. > > Thanks, > > -- > Bastien >
Re: org-babel-load-file support elisp
> On Feb 3, 2020, at 10:03 PM, Jack Kamm wrote: > > Tim Cross writes: > >> All other language specifiers comply to the pattern of source block >> languages being the language major mode name without the '-mode', but >> there is no elisp-mode. > > Sorry to be pedantic, but I think shell source blocks are another > exception here. [snip] FWIW, so are R and julia (ess-r-mode, ess-julia-mode) and c++ (cc-mode). I suspect more examples are "out there". Chuck
Re: Faster version of org-find-olp
Bastien writes: > Hi Adam, > > Adam Porter writes: > >> While working on org-recent-headings, I thought I needed a version of >> org-find-olp that behaved slightly differently, so I wrote a new >> function. > > thanks for working on such improvements. Is there something here we > can integrate in Org (master)? If possible, let's just optimize the > current functions with no added constraints or features, then see if > new options and features can be useful. I ended up writing a function on top of that that does find-or-create, so you can go to a certain outline path, creating and inserting (optionally in sorted order) the missing segments as you go. It was fairly difficult to get right, so perhaps it will be of use to someone, or appropriate for Worg or even Org proper: https://github.com/girzel/timesheet.el/blob/master/timesheet.el#L250 Yrs, Eric
Re: [O] MobileOrg and other tools
I'm not going to be critical of either MobileOrg or Orgzly, which are the way to go if you want a dedicated app. But I much prefer going to the trouble of setting up a Termux environment, which allows Emacs to run in a very close to native term mode on any Android device. I combine this with an rsync service and I have my working environment on two Linux desktops, three Linux laptops and three Android devices, including my phone. -- Bob Newell Honolulu, Hawai`i Via Linux/Emacs/Gnus/BBDB.
[PATCH] ob-sql.el support auto set sql-product in editing sql-mode src block buffer
I tried to write an alist of all database names. and write an function to used to match name to possible names. But I found this solution is a little kind of complicated. Another simple solution is just add an duplicate code of "postgresql" for alias "postgres". Because I found only one exception "postgresql" is "postgres" in ~sql-mode~ products alist. Other database names are matched with ~sql-mode~. So I decided to take the simpler solution. I attached patch in the email attachment. # == BTW, I'm still not good at Elisp, can't write out a good solution for translate and matching for database names. Here is my temporary databases alist: #+begin_src diff modified lisp/ob-sql.el @@ -87,6 +87,52 @@ (defconst org-babel-header-args:sql (database . :any)) "SQL-specific header arguments.") +(defcustom org-babel-sql-engines-alist nil + "Alist of engine names for :engine header argument. + +It is an alist data structure: ( . (list of alias names)). +Merged with sql-mode's `sql-product-alist'." + :type '(alist :key-type symbol :value-type list) + :group 'org-babel) + +;;; initialize `org-babel-sql-engines-alist' +(dolist (product (mapcar 'car sql-product-alist)) + (pcase product +(`ansi + (add-to-list 'org-babel-sql-engines-alist (cons 'ansi (list 'ansi +(`sqlite + (add-to-list 'org-babel-sql-engines-alist (cons 'sqlite (list 'sqlite +(`mysql + (add-to-list 'org-babel-sql-engines-alist (cons 'mysql (list 'mysql +(`mariadb + (add-to-list 'org-babel-sql-engines-alist (cons 'mariadb (list 'mariadb 'maria +(`postgresql + (add-to-list 'org-babel-sql-engines-alist (cons 'postgresql (list 'postgresql 'postgres +(`oracle + (add-to-list 'org-babel-sql-engines-alist (cons 'oracle (list 'oracle +(`mssql + (add-to-list 'org-babel-sql-engines-alist (cons 'mssql (list 'mssql 'ms +(`dbi + (add-to-list 'org-babel-sql-engines-alist (cons 'dbi (list 'dbi +(`monetdb + (add-to-list 'org-babel-sql-engines-alist (cons 'monetdb (list 'monetdb +(`sqsh + (add-to-list 'org-babel-sql-engines-alist (cons 'sqsh (list 'sqsh +(`vertica + (add-to-list 'org-babel-sql-engines-alist (cons 'vertica (list 'vertica +(`db2 + (add-to-list 'org-babel-sql-engines-alist (cons 'db2 (list 'db2 +(`infomix + (add-to-list 'org-babel-sql-engines-alist (cons 'infomix (list 'infomix +(`ingres + (add-to-list 'org-babel-sql-engines-alist (cons 'ingres (list 'ingres +(`interbase + (add-to-list 'org-babel-sql-engines-alist (cons 'interbase (list 'interbase +(`solid + (add-to-list 'org-babel-sql-engines-alist (cons 'solid (list 'solid +(`sybase + (add-to-list 'org-babel-sql-engines-alist (cons 'sybase (list 'sybase)) + (defun org-babel-expand-body:sql (body params) "Expand BODY according to the values of PARAMS." (org-babel-sql-expand-vars #+end_src I don't know how to write a translation function for alist to be used in function ~org-babel-execute:sql~. #+begin_src emacs-lisp :eval no (defun org-babel-execute:sql (body params) "Execute a block of Sql code with Babel. This function is called by `org-babel-execute-src-block'." (let* ((result-params (cdr (assq :result-params params))) (cmdline (cdr (assq :cmdline params))) (dbhost (org-babel-find-db-connection-param params :dbhost)) (dbport (org-babel-find-db-connection-param params :dbport)) (dbuser (org-babel-find-db-connection-param params :dbuser)) (dbpassword (org-babel-find-db-connection-param params :dbpassword)) (database (org-babel-find-db-connection-param params :database)) (engine (cdr (assq :engine params))) (colnames-p (not (equal "no" (cdr (assq :colnames params) (in-file (org-babel-temp-file "sql-in-")) (out-file (or (cdr (assq :out-file params)) (org-babel-temp-file "sql-out-"))) (header-delim "") (command (pcase (intern engine) (`dbi (format "dbish --batch %s < %s | sed '%s' > %s" (or cmdline "") (org-babel-process-file-name in-file) "/^+/d;s/^|//;s/(NULL)/ /g;$d" (org-babel-process-file-name out-file))) (`monetdb (format "mclient -f tab %s < %s > %s" (or cmdline "") (org-babel-process-file-name in-file) (org-babel-process-file-name out-file))) (`mssql (format "sqlcmd %s -s \"\t\" %s -i %s -o %s" (or cmdline "") (org-babel-sql-dbstring-mssql
Re: Bug: org-indent-region doesn't restore cursor position when org-src-tab-acts-natively is t [9.1.9 (release_9.1.9-65-g5e4542 @ /usr/share/emacs/26.3/lisp/org/)]
Hi Sébastien, Sébastien Miquel writes: > Thank you for your reply. > > I can still reproduce with latest Org Mh, yes, I can reproduce this now, and this is fixed in maint. Thanks! -- Bastien
Re: Bug: Scheduling capture with a single line capture template [9.2.4 (9.2.4-10-g3b006f-elpaplus @ /home/gustavo/.emacs.d/elpa/org-plus-contrib-20190715/)]
Hi Gustavo, Gustavo Barros writes: > thanks for looking into this. I managed to reproduce this bug, it is fixed in maint now. Thanks! -- Bastien
Re: [PATCH] Fix several issues with python session value blocks
Hi Bastien, Bastien writes: > Thanks a lot! Nitpicking, there is this new warning: > > In toplevel form: > ob-python.el:309:1: Warning: Unused lexical variable ‘last-indent’ > > Can you fix it? Oops, sorry for letting that slip through, and thanks for noticing so quickly. I've pushed a fix for this now. Cheers, Jack
Re: Glacial file operation!
Hi Sharon, Sharon Kimble writes: > So how can I either remove it, or negate its showing its effects in > every org-mode file please? Can you use `org-mode-hook' to deactivate whatever is getting in your way? -- Bastien
Glacial file operation!
I'm working with a series of files (its actually a website that I'm converting into a pdf, and exporting it from org-mode), and its becoming positively glacial in operation! And I think that 'wc-mode' is the culprit. And wc-mode is shown as a dependency in the paradox package-manager system. So how can I either remove it, or negate its showing its effects in every org-mode file please? I've commented it out in my config, but I'm still feeling its effects somehow. Thanks Sharon. -- A taste of linux = http://www.sharons.org.uk TGmeds = http://www.tgmeds.org.uk DrugFacts = https://www.drugfacts.org.uk Debian 10.2, fluxbox 1.3.7, emacs 26.3, org 9.3.2 signature.asc Description: PGP signature
Re: org-time-stamp keep the month and the year
Hi Uwe, Uwe Brauer writes: > Sometimes I have to insert various dates of a given month/year in a > table. However if this is not an actual date, every time I use > org-time-stamp I have to go back. > > On the other hand if this command is used twice in succession, a time > range is inserted. So in some way the same month/year is kept. > > Could I obtain this behavior although I don't use the command twice in > succession but move say the cursor. I don't really understand what you need - can you show us with an example table and timestamps? Thanks! -- Bastien
Re: Bug: Scheduling capture with a single line capture template [9.2.4 (9.2.4-10-g3b006f-elpaplus @ /home/gustavo/.emacs.d/elpa/org-plus-contrib-20190715/)]
Hi Bastien, thanks for looking into this. On Tue, Feb 04 2020, Bastien wrote: I cannot reproduce this issue with latest stable Org and emacs -q. Can you check and report if this still needs a fix? Yes, I can still reproduce this as described in the original report with current version (Org mode version 9.3.2 (9.3.2-24-g5c72d6-elpaplus @ /home/gustavo/.emacs.d/elpa/org-plus-contrib-20200203/)). As the recipe for the ECM starts with "emacs -Q", I don't know what else I could isolate in my environment. One possibility I can think of. It's been some time since I reported, but if I recall correctly, the existence of a headline *after* the one in which the capture is being placed was critical to the effect. Rereading the report, it is there in the ECM, but I haven't emphasized this in the analysis. Did you try the recipe with that file structure? But anyway, if you have any other ideas, I'm at your disposal to try things out and try to pin this further down. Best, Gustavo.
Re: A new, "org-bullets"-like minor mode
> > I would like to take a try too. Hope it is lightweight enough. Don't invoked > lot of time. > I have not yet optimized the package, but experience no issues. The package is currently in the process of being reviewed for MELPA. If you (or anyone else) would like to contribute a large, complex org file for benchmarking purposes I would be happy to profile my mode against it. For the time being, you can find it here: https://github.com/dw-github-mirror/org-superstar-mode
Re: [O] MobileOrg and other tools
Carsten Dominik writes: > I know that Orgzly is actively supported and in excellent shape. But I > don't know about MobileOrg or Syncorg for that matter, or any other similar > tools. https://beorgapp.com for iOS is actively developed and in a great shape. -- Toon
Re: Bug: python src var error [9.1.9 (release_9.1.9-65-g5e4542 @ /Applications/Emacs.app/Contents/Resources/lisp/org/)]
Hi Claire, Claire Chambers writes: > Hello! this webpage: https://orgmode.org/manual/var.html says that > unordered lists have nested elements ignored, but running the same code > snippet gives "| simple | (unordered (not) (nested)) | > | list ||", not "| simple | list |". I'm not sure I understand the problem. Can you tell us more about what you did, what you expected and what you got instead? Also, providing a minimal example that we can test in an org file can help. Please refer to https://orgmode.org/org.html#Feedback for further details on bug reports. Thanks, -- Bastien
Re: Title in an PlantUML generated file
Hi Cecil, Cecil Westerhof writes: > At the moment I am using PlantUML to generate eps diagrams. When > opening them in Evince it says: noTitle. Is there a way to get a > title so Evince has useful information in its window title? I guess the answer lies in PlantUML documentation. Did you try checking it out? -- Bastien
Re: Emacs master, faces with :extend t let cursor vanish at EOL?!
Hi Ingo, Ingo Lohmar writes: > Using this with a current elpa pkg of org-mode, and setting :extend t on > faces like `org-block`, "often" the cursor vanishes at the EOL of a line > using such a face. It reliably happens for `org-block', only sometimes > for `secondary-selection'. can you keep track of this issue and related discussions? I doubt there is anything we can do in Org itself, but perhaps a hint in a docstring could help. Let us know, thanks, -- Bastien
Re: Bug: Comments and Hiding of Emphasis Markers [9.2.6 (release_9.2.6-539-g1fd07c @ /home/w/borg/emacs/org/lisp/)]
Hi Sebastian, Sebastian Miele writes: > An Org file like > > # -*- lexical-binding: t; -*- > *bold* > > is dispayed as > > # -- lexical-binding: t; -- > bold > > where 'bold' is bold and '- lexical-binding: t; -' is not. Expected: In > comments emphasis marker characters are no emphasis markers and despite > hiding of emphasis markers, something like '# *a*' is still dispayed as > '# *a*'. Indeed. Emphasis markers are not hidden in comments in Org master. Some people may want to hide them here anyway: perhaps we can make the `org-hide-emphasis-markers' option a little more clever. Thanks, -- Bastien
Re: [ANN] helm-org-ql command
Hi Adam, Adam Porter writes: > Today I published a Helm command for org-ql, helm-org-ql, which makes it > quick and easy to search Org files. looks nice! If you find a way to advertize this in Worg, please go ahead. If you don't find a way, well, probably you can create a new section or page in Worg for these external packages. Thanks, -- Bastien
Re: Unschedule an item from the date prompt
Hi Nathan, Nathan Neff writes: > I seem to remember a way to unschedule an item > from the date prompt. I found: > https://orgmode.org/manual/The-date_002ftime-prompt.html I don't remember any such feature, but who knows? If you found it in the meantime, please let us know. Thanks! -- Bastien
Re: MobileOrg and other tools
Hi Jean, Jean Louis writes: > * Carsten Dominik [2019-08-18 13:41]: >> does anyone know if the MobileOrg apps for both iOS and Android are still >> supported, and by who? > > I prefer that MobileOrg options are removed from Org menu in > Emacs. Just my opinion. It is not necessary. Agreed. From master, the Mobile menu entry is only displayed when the 'org-mobile feature is explicitely required by the user. Thanks, -- Bastien
Re: [PATCH] Fix several issues with python session value blocks
Hi Jack, Jack Kamm writes: > Kyle Meyer writes: > >>> I'd like to do the honors of making my first push to the repo :) So >>> please let me know if you're fine with me to proceed. >> All good from my end :> > > Thanks -- I've pushed to master :D Thanks a lot! Nitpicking, there is this new warning: In toplevel form: ob-python.el:309:1: Warning: Unused lexical variable ‘last-indent’ Can you fix it? Thanks again, -- Bastien
Re: Faster version of org-find-olp
Hi Adam, Adam Porter writes: > While working on org-recent-headings, I thought I needed a version of > org-find-olp that behaved slightly differently, so I wrote a new > function. thanks for working on such improvements. Is there something here we can integrate in Org (master)? If possible, let's just optimize the current functions with no added constraints or features, then see if new options and features can be useful. Thanks! -- Bastien
Re: org-cell in org-table with a list or a new paragraph
Hi, flow writes: > I was wondering if I can get a new line inside the cell of a table in > Orgmode to be rendered as new paragraph or as a list. Hitting M-RET in a table's cell will open a new cell below and allow you to use "-" for a list item, but this list item won't be recognized as such when exporting. We cannot support list items within tables for export, this would be too complex and possibly confusing. -- Bastien
Re: [Feature proposal] Add :description function to org-link-parameters
Hi Ihor, Ihor Radchenko writes: > Wondering if anyone is interested in adding a new org-link property to > customise generating the link description. yes, this sounds useful. Can you propose a patch against current Org master branch? See https://orgmode.org/worg/org-contribute.html on how to contribute. If you need to contribute more than 15 lines of code or want to be able to contribute later on, please fill this form: https://code.orgmode.org/bzg/org-mode/raw/master/request-assign-future.txt Also, as John noted already, "desk" is confusing, you can simply use "description" (long names are not a problem.) Thanks in advance! -- Bastien
Re: feature request: modify org-attach to also create new (non-text) attachments
Hi Simon, Simon Campese writes: > while in orgmode, I frequently create some handwritten notes (using > a wacom tablet and xournalpp) and attach it to the current > headline. My ad-hoc solution is the following trivial modification of > org-attach-new (only the second to last line has changed): if this is still relevant, can you send a patch against org-attach.el from the master branch? See https://orgmode.org/worg/org-contribute.html on how to contribute. Thanks, -- Bastien
Re: Bug: Scheduling capture with a single line capture template [9.2.4 (9.2.4-10-g3b006f-elpaplus @ /home/gustavo/.emacs.d/elpa/org-plus-contrib-20190715/)]
Hi Gustavo, Gustavo Barros writes: > When using a single line capture template for an entry, the indirect buffer > where the capture editing occurs restrains itself to that single line. As a > consequence, scheduling during capture is not visible in the capture > buffer. I cannot reproduce this issue with latest stable Org and emacs -q. Can you check and report if this still needs a fix? Thanks, -- Bastien
Re: org-scheduled-time-hour-regexp doesn't capture split repeats used by habit
Hi Damian, > The ':scheduled*' value for org-agenda-entry-types uses > org-scheduled-time-hour-regexp to match related entries. The current > regexp doesn't match entries with split repeats like those used by > habits- for example: 'SCHEDULED: <2019-06-25 Tue 20:30 > .+1d/2d>'. Because those entries show up in the agenda with a > timestamp I believe they should be caught by the regexp. thanks for reporting this, this is now fixed in the maint branch. -- Bastien
