Adam Spiers writes:
> I've noticed that adding the :STYLE: habit property to a TODO causes
> its position in the agenda view to change; it jumps to the bottom of
> the day. Is there any way to prevent that?
Try customizing org-agenda-sorting-strategy (in particular, dropping
habit-down from agen
Kyle Meyer writes:
> Kyle Meyer writes:
>
>> Ken Mankoff writes:
>>
>>> ob-screen prepends "org-babel-session-" to the user-specific screen
>>> name for some reason. I suggest this is not necessary nor optimal. One
>>> of the key points of 'screen' is that you can detach and attach from
>>> elsewh
Ken Mankoff writes:
> Last ob-screen patch. I apologize if these should have been one email
> but they are there independent issues.
>
> This patch maintains the default behavior of no screenrc "-c
> /dev/null", but adds a :screenrc header arg that allows the user to
> specify their default or any
Ken Mankoff writes:
> I've signed the FSF docs but do not see my name here:
> https://orgmode.org/worg/org-contribute.html under "Current
> contributors".
Thanks for the information. I'll add you to the list.
> Subject: [PATCH 1/3] ob-screen: Execute last line in block (send newline)
Could you
Hi there,
I recently updated my emacs packages and noticed that \begin{align*}
does not trigger math-mode detection any more, so org-cdlatex does not
work. However, begin{equation} still does trigger the math-mode
detection. I have read the documentation of
"org-inside-LaTeX-fragment-p" and found
Hello, I've made a patch for `ob-haskell.el`.
I'm not really an elisper, but I made a patch that seems to work on my machine.
Issue: compiling code in a source block that had an infinite list that would
evaluate in the ghci.
All code, even with `:compile` flag set would be run in ghci.
Updating
Hello,
The attached three patches implement a bug fix, a simplification, and a new
feature to ob-screen.
bug fix: 001 Execute last line in block (send newline)
simplify: 002 Don't add extra characters to session name
feature: 003 Accept :screenrc header argument
I've signed the FSF docs but do
Many thanks indeed,
>
> I have the following settings,
>
> (modify-syntax-entry ?< ".")
> (modify-syntax-entry ?> ".")
>
> in my org mode hook. This stops org from treating them as parenthesis.
Best regards,
Jeremie
Bo, you can try this. I don't know what else it will break, so I did it as
a file local. alternatively you could set `org-match-substring-regexp' in
your init.
---
;;; -*- org-match-substring-regexp:
"\\(\\)\\([_^]\\)\\(\\(?:{\\([^{}]*?\\|\\(?:[^{}]*?{[^{}]*?}\\)+[^{}]*?\\|\\(?:[^{}]*?{\\(?:[^{}]*
Hello,
Matt Lundin writes:
> When there is an active region, the function org-fill-paragraph does not
> limit itself to the active region but also fills the paragraph before
> the active region.
>
> Steps to reproduce. Use the following file. Mark the last two entry
> paragraphs, beginning at "L
>>> "UB" == Uwe Brauer writes:
> Hi
> Consider please the following to tables
> #+begin_src
> ,#+TBLNAME: test3
> | Email | State|
> |-+--|
> | us...@gmail.com | Sent |
> | us...@gmail.com | not sent |
> ,#+TBLNAME: test4
> | Email | Sta
Hi
Consider please the following to tables
#+begin_src
,#+TBLNAME: test3
| Email | State|
|-+--|
| us...@gmail.com | Sent |
| us...@gmail.com | not sent |
,#+TBLNAME: test4
| Email | State |
|+-|
| us
12 matches
Mail list logo
