Eli Zaretskii writes:
>> From: Robert Pluim
>> Cc: Eli Zaretskii , 34...@debbugs.gnu.org
>> Date: Fri, 01 Mar 2019 11:00:01 +0100
>>
>> > It could be some snafu in Org, though, e.,g. if it doesn't know how to
>> > support that value of $LANG. In any case, should be reported to Org
>> >
Robert Pluim writes:
> Eli Zaretskii writes:
>
>>> From: Robert Pluim
>>> Cc: Eli Zaretskii , 34...@debbugs.gnu.org
>>> Date: Fri, 01 Mar 2019 11:00:01 +0100
>>>
>>> > It could be some snafu in Org, though, e.,g. if it doesn't know how to
>>> > support that value of $LANG. In any case,
> From: Robert Pluim
> Cc: Eli Zaretskii , 34...@debbugs.gnu.org
> Date: Fri, 01 Mar 2019 11:00:01 +0100
>
> > It could be some snafu in Org, though, e.,g. if it doesn't know how to
> > support that value of $LANG. In any case, should be reported to Org
> > developers first.
>
>
Eli Zaretskii writes:
>> Iʼm assuming thereʼs an issue with buffer-file-coding-system or
>> similar.
>
> Unlikely: buffer-file-coding-system has no effect whatsoever on the
> text that is inserted into a buffer, it only has effect when you want
> to save the buffer or send it to some
> From: Robert Pluim
> Cc: "Wong\, Philip" , 34...@debbugs.gnu.org
> Date: Thu, 28 Feb 2019 20:11:45 +0100
>
> Eli Zaretskii writes:
>
> >> From: "Wong, Philip"
> >> Date: Thu, 28 Feb 2019 14:16:25 +
> >>
> >> When I insert a date by pressing CTRL+C then period then enter I get
> >>
Robert Pluim writes:
> Eli Zaretskii writes:
>
>>> From: "Wong, Philip"
>>> Date: Thu, 28 Feb 2019 14:16:25 +
>>>
>>> When I insert a date by pressing CTRL+C then period then enter I get
>>> “<2019-02-28 ¶g¥|>”.
>>>
>>> I’m not sure what the strange character is (¶g¥|), can someone
Eli Zaretskii writes:
>> From: "Wong, Philip"
>> Date: Thu, 28 Feb 2019 14:16:25 +
>>
>> When I insert a date by pressing CTRL+C then period then enter I get
>> “<2019-02-28 ¶g¥|>”.
>>
>> I’m not sure what the strange character is (¶g¥|), can someone help?
>
> Please show a complete
On 28 Feb 2019, at 11:02, Nicolas Goaziou wrote:
Hello,
"Galen Menzel" writes:
I’m seeing that in org 9.2.1 (from org-plus-contrib 20190225)
tables
are not respecting column-width specifications. For example, if
I create the following table
| Header 1
Hello,
"Galen Menzel" writes:
> I’m seeing that in org 9.2.1 (from org-plus-contrib 20190225) tables
> are not respecting column-width specifications. For example, if
> I create the following table
>
> | Header 1 |
> | <10>
Oops, forgot to include verbatim markers.
For the following table
```
| Header 1 |
| <10> |
| This column should be truncated to 10 characters |
```
When I align it in org 9.1.9, the column display is truncated
Hi all,
I’m seeing that in org 9.2.1 (from org-plus-contrib 20190225) tables
are not respecting column-width specifications. For example, if I create
the following table
| Header 1 |
| <10> |
| This column
> From: "Wong, Philip"
> Date: Thu, 28 Feb 2019 14:16:25 +
>
> When I insert a date by pressing CTRL+C then period then enter I get
> “<2019-02-28 ¶g¥|>”.
>
> I’m not sure what the strange character is (¶g¥|), can someone help?
Please show a complete recipe, starting from "emacs -Q", to
On Thursday, 21 Feb 2019 at 20:42, Nick Helm wrote:
> Eric S Fraga writes:
>
>> It would be great, for others that may be interested, if you could post
>> your solution to this list.
>
> Here's an alternative way to achieve this with today's master.
Thank you.
--
Eric S Fraga via Emacs 27.0.50,
On 2019-02-26 09:14, Nicolas Goaziou
writes:
I think the problem is on line 3036 of org-agenda.el. The code
(propertize match nil 'face 'org-warning))
should be
(propertize match 'face 'org-warning))
(I changed it locally and
Hello,
Alan Schmitt writes:
> On 2019-02-26 02:19, Gustavo Barros writes:
>
>> I've been having trouble with my custom agenda commands since the
>> latest
>> update.
>>
>> The agenda dispatcher used to work fine until the last update, but
>> now,
>> given one of my custom agenda commands, it
On 2019-02-26 02:19, Gustavo Barros
writes:
I've been having trouble with my custom agenda commands since
the latest
update.
The agenda dispatcher used to work fine until the last update,
but now,
given one of my custom agenda commands, it issues the error
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.
Hello,
Allen Li writes:
> Subject: [PATCH] Fix buffer local org-agenda-overriding-columns-format bug
>
> Setting org-agenda-overriding-columns-format as a buffer local value
> interferes with how it is used as a dynamically scoped var, so use a
> separate variable for buffer local setting.
Thank you for the comments, attached new patch.
On Mon, Feb 18, 2019 at 9:16 PM Nicolas Goaziou wrote:
>
> > (defun org-agenda-finalize ()
> >"Finishing touch for the agenda buffer, called just before displaying
> > it."
> >(unless org-agenda-multi
> > @@ -3783,7 +3784,7 @@
Hello,
"Eugene Sharygin" writes:
> I have `org-log-refile` in my configuration set to `time`, which makes
> `org-refile` add a time stamp to the LOGBOOK drawer at the target
> location.
>
> However, when `org-refile` is called with active region containing
> multiple entries, only LOGBOOK of
Hi,
I have `org-log-refile` in my configuration set to `time`, which makes
`org-refile` add a time stamp to the LOGBOOK drawer at the target
location.
However, when `org-refile` is called with active region containing
multiple entries, only LOGBOOK of the first entry is updated.
For example,
Hello,
"Dietrich Foethke" writes:
> suppose I create an org file and I would like to insert a link to a
> foreign website called "http://www.mypage.org; with an image as
> description. For the image I use the local image "images/example.jpg".
> The corresponding line in org would read:
>
>
Hello,
Consider the following HTTP link:
http://skyserver.sdss.org/dr14/en/tools/quicklook/summary.aspx?ra=11%2054%2048.85=+24%2043%2033.0
I have this link in the kill-ring, mark 'some text' in an org-mode buffer
and run org-insert-link (C-c C-l). Then I yank the link (C-y) in the
minibuffer,
Eric S Fraga writes:
> It would be great, for others that may be interested, if you could post
> your solution to this list.
Here's an alternative way to achieve this with today's master.
--- a/lisp/org-table.el 2019-02-21 21:28:34.0 +1300
+++ b/lisp/org-table.el 2019-02-21
Hello,
Duane Farnsworth writes:
> Setting org-icalendar-include-todo to unblocked does not seem to work.
> I would expect unblocked TODO entries to be exported as VTODO entries
> in the .ics-extension file generated by
> org-icalendar-export-agenda-files. Instead, no plain TODO entries are
>
Hi,
suppose I create an org file and I would like to insert a link to a
foreign website called "http://www.mypage.org; with an image as
description. For the image I use the local image "images/example.jpg".
The corresponding line in org would read:
Hello,
Éibhear writes:
> I believe there is a bug in the preparation of a clock report when the
> :step parameter is set.
>
> Example:
>
> * Headline 1
> :LOGBOOK:
> CLOCK: [2019-02-20 Wed 08:39]--[2019-02-20 Wed 14:05] => 5:26
> CLOCK: [2019-02-19 Tue 13:38]--[2019-02-19 Tue
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.
Hi,
I believe there is a bug in the preparation of a clock report when the
:step parameter is set.
Example:
* Headline 1
:LOGBOOK:
CLOCK: [2019-02-20 Wed 08:39]--[2019-02-20 Wed 14:05] => 5:26
CLOCK: [2019-02-19 Tue 13:38]--[2019-02-19 Tue 17:48] => 4:10
CLOCK: [2019-02-19 Tue
Hello,
John Borwick writes:
> If I execute in *scratch*
>
> (org-agenda-get-day-entries "~/Dropbox/org/main-todo.org" '(2 18 2019)
> :deadline :scheduled :timestamp :sexp)
>
> and main-todo.org contains this entry:
>
> *** TODO Medium priority inboxes
>
Hello,
Nick Helm writes:
> When the specified column width is one or two characters wider than the
> longest cell in the column (26 and 27 char in the example below), the
> shrunk column indicator and right-hand table borders do not draw
> correctly.
>
> For example, shrink the following with
Nicolas Goaziou writes:
> Anyway, I changed the algorithm, so shrinking should now obey to
> alignment.
By the way, I think this change may have introduced a new bug.
When the specified column width is one or two characters wider than the
longest cell in the column (26 and 27 char in the
Eric S Fraga writes:
> On Tuesday, 19 Feb 2019 at 03:16, Nick Helm wrote:
>
> [...]
>
>> Great, got it sorted now. Thanks again for your time.
>
> It would be great, for others that may be interested, if you could post
> your solution to this list.
Sure, patch below. It's a bit crude, but it
On Tuesday, 19 Feb 2019 at 03:16, Nick Helm wrote:
[...]
> Great, got it sorted now. Thanks again for your time.
It would be great, for others that may be interested, if you could post
your solution to this list.
thanks,
--
Eric S Fraga via Emacs 27.0.50, Org release_9.2-193-ge7901c
Nicolas Goaziou writes:
> Nick Helm writes:
>
>> Could you tell me what functions govern this feature?
>
> You may want to have a look into `org-table--shrink-field' and
> `org-table--make-shrinking-overlay'.
Great, got it sorted now. Thanks again for your time.
Nick Helm writes:
> That's a shame.
Feel free to demonstrate a practical use-case, if you want to.
> Could you tell me what functions govern this feature?
You may want to have a look into `org-table--shrink-field' and
`org-table--make-shrinking-overlay'.
Regards,
Hello,
Jeffrey Spencer writes:
> The first two work below but going from alphabetical to unordered list
> (second two)
> doesn't work. Is there a reason or way to fix this?
>
> (setq org-list-demote-modify-bullet
> '(("1." . "+") ("A." . "a.") ("a." . "+") ("A)" . "+")))
Fixed. Thank you.
Nicolas Goaziou wrote:
> Hello,
>
> Piet van Oostrum writes:
>
> > In org-mode 9.2.1, the menu item Org > Show/Hide > Show All is bound
> > to org-show-all, but this function is nor=t interactive. Therefore the
> > invocation of this menu item fails.
> >
> > command-execute: Wrong
Nicolas Goaziou writes:
> Nick Helm writes:
>
>> But, the rest of the time, can't the indicator serve both purposes -
>> indicate a shrunken column and the presence of truncated cells - when it
>> is limited to places where text is hidden?
>
> I find it confusing -- you may actually miss the
Hello,
Nick Helm writes:
> But, the rest of the time, can't the indicator serve both purposes -
> indicate a shrunken column and the presence of truncated cells - when it
> is limited to places where text is hidden?
I find it confusing -- you may actually miss the information that the
current
Hello,
Allen Li writes:
> I have attached a patch implementing this on maint.
Thank you. Some comments follow.
> Subject: [PATCH] Fix buffer local org-agenda-overriding-columns-format bug
>
> Setting org-agenda-overriding-columns-format as a buffer local value
> interferes with how it is used
Hello,
Piet van Oostrum writes:
> In org-mode 9.2.1, the menu item Org > Show/Hide > Show All is bound
> to org-show-all, but this function is nor=t interactive. Therefore the
> invocation of this menu item fails.
>
> command-execute: Wrong type argument: commandp, org-show-all
>
> Solution:
Sorry, you are right. I was reading the 9.1.9 manual, so I expected a call to
org-table-align
would collapse the columns accordingly to their width tokens
Thanks
Joao Cortes
From: Nicolas Goaziou
Sent: 18 February 2019 16:05
To: Joao Cortes
Cc:
Hello,
Joao Cortes writes:
> It seems imposing a constant width to a column no longer works,
>
> | 1 |
> ||
> | <3>|
> | 123456 |
> ||
FWIW, I cannot reproduce anything wrong with that table.
Regards,
--
Nicolas Goaziou
It seems imposing a constant width to a column no longer works,
| 1 |
||
| <3>|
| 123456 |
||
After rolling back to 9.1.14 It works again,
| 1 |
|---|
| <5> |
| 12 34 |
|---|
Emacs : GNU Emacs 26.1 (build 1, x86_64-redhat-linux-gnu, GTK+ Version
Nicolas Goaziou writes:
> Anyway, I changed the algorithm, so shrinking should now obey to
> alignment. Thank you for the feedback.
Thank you – this is a welcome improvement.
>> | <5> …|
>> | one …|
>> | one …|
>>
>> This is misleading - cell 3 contains no additional content yet the
>>
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.
Hello,
Nick Helm writes:
> If that's the case, it's a significant loss of functionality. This would
> mean, for instance, that it's no longer possible to format financial
> data with a uniform column width.
"significant" may be relative. The feature has been available on master
for months, and
On Wed, Feb 13, 2019 at 8:17 AM Allen Li wrote:
>
> 0. Make /tmp/tmp.org containing
>
> * TODO foo bar
>
> 1. emacs -Q
> 2. Eval (setq org-agenda-custom-commands '(("n" "n" alltodo ""
> ((org-agenda-overriding-columns-format "%TODO")
> 3. Eval (setq org-agenda-files '("/tmp/tmp.org"))
> 4.
Thank you for your response.
Nicolas Goaziou writes:
> Nick Helm writes:
>>
>> The column is no longer right aligned.
>
> This is by design, so you can often edit the field without expanding the
> column.
I'm not sure I follow. Are you saying the ability align cell contents in
a shrunk
Hello,
Nick Helm writes:
> Create a new table:
[...]
> | |
> | one |
> | two is a longer cell |
>
> and shrink to size with C-c TAB:
>
> |…|
> | one …|
> | two is a longer cell
Hello,
I’d forgotten to CC the list in my previous message, so I’ve included
all the context from our two previous emails.
Nicolas Goaziou writes:
> Leo Vivier writes:
>
>> You’re right, that’s the behaviour we would expect from M-RET. However,
>> with C-RET, the new heading should respect
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.
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.
Hello,
Alex Branham writes:
> On the tip of the maint branch
> (8fc22d464d2bc4a3397516854375b177835d10bb) any call to functions like
> 'org-todo' results in an error 'void-function org-clock-out-if-current'.
>
> Here's a sample backtrace:
>
> Debugger entered--Lisp error: (void-function
Hello -
On the tip of the maint branch
(8fc22d464d2bc4a3397516854375b177835d10bb) any call to functions like
'org-todo' results in an error 'void-function org-clock-out-if-current'.
Here's a sample backtrace:
Debugger entered--Lisp error: (void-function org-clock-out-if-current)
Hello,
Leo Vivier writes:
> The bug only happens in narrowed org-mode buffers when the tree at
> point (or targeted by the resolving) is a single line not followed by a
> blank line.
[...]
> MWE:
>
> [START]
> * Tree 1
> * Tree 2
Hello,
Carlos Pita writes:
> I think your refactor improves the original code a lot and makes clear
> that toggling is just a special case.
>
> I've been testing the changes with a pretty complex beamer document
> and found no fault.
Great! Thank you for the feedback and the suggested
> Please let me know if anything went wrong.
I think your refactor improves the original code a lot and makes clear
that toggling is just a special case.
I've been testing the changes with a pretty complex beamer document
and found no fault.
Thanks!
Carlos Pita writes:
> Nicolas, here is a patch implementing alternative B above with
> ORG-NEWS entry and everything.
>
> I have been playing with it and find the bindings quite handy.
>
> Code is indeed a bit simpler.
>
> If you like it, feel free to amend it before merging.
Thank you.
I
Nicolas, here is a patch implementing alternative B above with
ORG-NEWS entry and everything.
I have been playing with it and find the bindings quite handy.
Code is indeed a bit simpler.
If you like it, feel free to amend it before merging.
Best regards
--
Carlos
From
Ok, let's make this more concrete so I can start working on it then.
Alternative A:
Provide three functions:
org-toggle-latex-fragment:
bound to C-c C-x C-l
has an optional argument arg
delegates to org-preview-latex-section if necessary (outside of
fragment or C-u)
Carlos Pita writes:
>> C-c C-x C-l: as you defined it
>> C-u C-c C-x C-l: preview document scope.
>> C-- (or C-0) C-c C-x C-l: as you defined C-u C-c C-x C-l.
>> C-- (or C-0) C-u C-c C-x C-l: unpreview document scope.
>
> Btw, I don't think that "preview the entire document" is such a rare
> use
> C-c C-x C-l: as you defined it
> C-u C-c C-x C-l: preview document scope.
> C-- (or C-0) C-c C-x C-l: as you defined C-u C-c C-x C-l.
> C-- (or C-0) C-u C-c C-x C-l: unpreview document scope.
Btw, I don't think that "preview the entire document" is such a rare
use case. Consider that you've
> WDYT?
I like it. Indeed, I was tempted to suggest removing document scope
but, as an end user, I moderate my proposals to be more or less
conservative.
There are some complications though. If we remove the document scope
bindings we have to refactor the current function quite a bit, because
Hello,
Carlos Pita writes:
> So lets play with minus as a modifier, I like that idea.
>
> (A) Here is a variation of my proposal:
>
> [C- -] [C-u] [C-u] C-c C-x C-l
>
> The modifier [C- -] means force preview.
> The modifier [C-u] means section scope.
> The modifier [C-u][C-u] means document
Hello,
Josiah Schwab writes:
> See discussion at
> https://lists.gnu.org/archive/html/emacs-devel/2019-02/msg00238.html
>
> Sounds like it was fixed in master, but maybe not in maint.
Since the fix is innocuous, I just backported it to maint, too.
Regards,
--
Nicolas Goaziou
See discussion at
https://lists.gnu.org/archive/html/emacs-devel/2019-02/msg00238.html
Sounds like it was fixed in master, but maybe not in maint.
Josiah
I tried to publish a project on Emacs 25.2.1 and received an arithmetic
out of range error on a call to floor. The problem seems to be a call
to floor during the caching process that's out of the 32-bit integer range.
Backtrace follows:
Debugger entered--Lisp error: (range-error "floor"
Also, make sure imagemagick is installed.
Btw, you might find this useful for previewing babel-generated images:
(defun my-org-babel-redisplay-images ()
(when org-inline-image-overlays
(org-redisplay-inline-images)))
(add-hook 'org-babel-after-execute-hook
Hi,
> #+HEADER: :file latex.svg
> #+HEADER: :results drawer
> #+BEGIN_SRC latex
I think you're missing some headers to get it working. For example, I
use the following defaults to preview/export images generated with
tikz to html/markdown documents:
Hello,
Carlos Pita writes:
> Not a big deal, but here is a slightly better fix that avoids adding
> some spaces before the closing }.
>
> The difference wrt to the previous one is just:
>
> - (unless (memq (caar tbl) '(:endgroup :endgrouptag)) (insert "\n"))
> - (when (or
Consider this latex source block,
#+HEADER: :file latex.svg
#+HEADER: :results drawer
#+BEGIN_SRC latex
\begin{tikzpicture}
\draw[red] (0,0) circle (1cm);
\end{tikzpicture}
#+END_SRC
I would like to preview the result inline using
Apologies for the spam.
On Wed, Feb 13, 2019 at 9:11 AM Allen Li wrote:
> I don't see an easy good fix due to how Emacs's dynamic variable
> binding works with respect to buffer local variables.
>
> One way to fix is redefine:
>
> (defun org-let (list body)
> (eval `(with-temp-buffer ,(cons
On Wed, Feb 13, 2019 at 8:37 AM Allen Li wrote:
>
> I'm suspicious of org-agenda-mode -> kill-all-local-variables=
>
> One oddity is that repeatedly reverting the buffer swaps between the
> "correct" overriding column format and the default.
It seems like what is happening is that the
On Wed, Feb 13, 2019 at 8:17 AM Allen Li wrote:
>
> 0. Make /tmp/tmp.org containing
>
> * TODO foo bar
>
> 1. emacs -Q
> 2. Eval (setq org-agenda-custom-commands '(("n" "n" alltodo ""
> ((org-agenda-overriding-columns-format "%TODO")
> 3. Eval (setq org-agenda-files '("/tmp/tmp.org"))
> 4.
0. Make /tmp/tmp.org containing
* TODO foo bar
1. emacs -Q
2. Eval (setq org-agenda-custom-commands '(("n" "n" alltodo ""
((org-agenda-overriding-columns-format "%TODO")
3. Eval (setq org-agenda-files '("/tmp/tmp.org"))
4. M-x org-agenda RET n
5. Move point to item
6. C-c C-x C-c (column
> `C-c C-x C-S-l` is too ugly, even for me. It is a convention we don't
> use in Org.
Mmm ok :).
I proposed it because it is easy to remember if you think you're
modifying a base action by S and also because it's easier to keep C
pressed (versus simply S-l or M-l).
So lets play with minus as a
Carlos Pita writes:
> What about leaving everything as it is now and adding C-c C-x C-S-l to mean
> "force preview", of course with the C-u and C-u C-u variants. This is a bit
> more orthogonal in the sense that the numerical argument controls scope and
> the S modifier controls "forcing". Also,
What about leaving everything as it is now and adding C-c C-x C-S-l to mean
"force preview", of course with the C-u and C-u C-u variants. This is a bit
more orthogonal in the sense that the numerical argument controls scope and
the S modifier controls "forcing". Also, it's backwards compatible
Hello,
Carlos Pita writes:
> A last suggestion. Incidentally the toggle returns nil when at least a
> fragment is unpreviewed and non-nil otherwise (as a side effect of
> message). This can be documented and made part of the interface, so
> that something like the following can be put together
Not a big deal, but here is a slightly better fix that avoids adding
some spaces before the closing }.
The difference wrt to the previous one is just:
- (unless (memq (caar tbl) '(:endgroup :endgrouptag)) (insert "\n"))
- (when (or ingroup intaggroup) (insert " "))
+
Ok, this was easier than I initially thought.
Here is a patch. I've tested it with a number of configurations: a few
grouped tags, many grouped tags, grouped tags that fill the last line
entirely, grouped and ungrouped tags. Notice that even ungrouped tags
are indented by two spaces. This is done
For example, with:
#+tags: { @casa(c) @oficina(o) @viaje(v) @gimnasio(g) @xxx(x) }
I get:
{ [c] @casa [o] @oficina[v] @viaje [g] @gimnasio
[x] @xxx}
where [c] and [x] are clearly misaligned.
If I remove the last tag:
#+tags: { @casa(c) @oficina(o) @viaje(v)
>>> "NG" == Nicolas Goaziou writes:
> Hello,
> Uwe Brauer writes:
>> In an org file
>>
>> 1. I run org-agenda
>>
>> 2. Then m (for search tags)
>>
>> 3. Then the tag, which is displayed but also an annoying error
>> message which I attach
> It doesn't look
Hello,
"Dietrich Foethke" writes:
> Description: I use a master org file "master.org" in a directory named
> "foo" that includes another org file "other.org" stored in subdirectory
> named "foo/bar". In the master file I include the other org file using:
>
> #+INCLUDE: "./bar/other.org"
>
> In
A last suggestion. Incidentally the toggle returns nil when at least a
fragment is unpreviewed and non-nil otherwise (as a side effect of
message). This can be documented and made part of the interface, so
that something like the following can be put together by the end user:
(defun
> I suggest to make C-c C-x C-l a toggle with preference for previewing,
> that is: preview everything except when everything is already previewed.
Mmmm I think this is not easy since it would imply changing
org-remove-latex-fragment-image-overlay return value:
(if
> the current section. Now, there is C-u C-u C-c C-x C-l for that. AFAICS,
Sorry I meant just one C-u.
C-u C-u is to clear the entire buffer of previews.
According to the docstring:
```
(defun org-toggle-latex-fragment ( arg)
"Preview the LaTeX fragment at point, or all locally or globally.
If the cursor is on a LaTeX fragment, create the image and overlay
it over the source code, if there is none. Remove it otherwise.
**If there is no
>>> "NG" == Nicolas Goaziou writes:
> Hello,
> Uwe Brauer writes:
>> In an org file
>>
>> 1. I run org-agenda
>>
>> 2. Then m (for search tags)
>>
>> 3. Then the tag, which is displayed but also an annoying error
>> message which I attach
> It doesn't look
Hello,
Uwe Brauer writes:
> In an org file
>
> 1. I run org-agenda
>
> 2. Then m (for search tags)
>
> 3. Then the tag, which is displayed but also an annoying error
>message which I attach
It doesn't look like an Org bug. You may need to update BBDB (mine, 3.2,
contains
Hi
In an org file
1. I run org-agenda
2. Then m (for search tags)
3. Then the tag, which is displayed but also an annoying error
message which I attach
Regards
Uwe Brauer
Debugger entered--Lisp error: (error "Autoloading file
Hello,
Version info:
- Emacs : GNU Emacs 26.1 (build 1, x86_64-pc-linux-gnu, GTK+ Version
3.22.30), of 2018-07-05
- Package: Org mode version 9.2.1 (9.2.1-2-gc6d37c-elpaplus)
The bug only happens in narrowed org-mode buffers when the tree at
point (or targeted by the resolving) is a single
Hello,
Felix Wiemuth writes:
> Start with an empty buffer in org-mode and add the following content:
>
> * A
> - L1
> - L2
> * B
>
> If we execute `org-list-make-subtree` on any position within the list (the
> two lines with L1/L2), we get
>
> * A
> ** L1
> ** L2* B
>
> So the conversion
Hello,
Ernesto Alfonso writes:
> The following URLs fail to get inlined as an html image:
>
> https://travis-ci.org/erjoalgo/emacs-buttons.svg?branch=master
> https://travis-ci.org/erjoalgo/emacs-buttons.png?branch=master
>
> But this one does:
>
>
Tables with multibyte characters and ASCII are not aligned properly after
org-table-align in GUI mode.
In -nw mode table is properly aligned, but its incorrect in GUI mode.
Steps to reproduce:
Start emacs in GUI mode. Copy and paste table below to org-mode buffer. Put
emacs cursor inside the
Hello,
Glenn Morris writes:
> It's due to the eval-when-compile sections in org-odt-schema-dir-list
> and org-odt-styles-dir-list. These don't make sense to me. All they do
> is add the build directory. There is a comment "see make install", but I
> cannot see what this refers to. No similar
Description: I use a master org file "master.org" in a directory named
"foo" that includes another org file "other.org" stored in subdirectory
named "foo/bar". In the master file I include the other org file using:
#+INCLUDE: "./bar/other.org"
In "other.org" I include an image that is stored in
It's due to the eval-when-compile sections in org-odt-schema-dir-list
and org-odt-styles-dir-list. These don't make sense to me. All they do
is add the build directory. There is a comment "see make install", but I
cannot see what this refers to. No similar variable initializes itself
in this way
301 - 400 of 9192 matches
Mail list logo
