ing
(add-hook 'org-mode-hook #'org-num-mode)
in my init file. org-num-mode worked fine for me.
Just one idea came to my mind. What about adding an option to restart
the numbering at 1 for the first heading in the case when narrowing is
in effect?
Ciao, Marco
ert!
Occasionally I like to bend time to see what the agenda would look like
if another day was current. This can be achieved conveniently when
solely function "current-time" is the source for the current time.
So I'm all for using the explicit calls to current-time instead of using
alternatve sources for the current time.
My 2ct, Marco
be a time travel feature in Org this feature should be
made explicit, I think, which BTW could be ensured with suitable tests.
Possibly one could use external tools to get even more powerful
timetravel, as Marcin proposed IIRC.
So go ahead with every optimization you can find!
Best regards, Marco
terest
we could just not commit the patch.
If there is interest in that patch, the code could be refined to only
hook into the `post-command-hook' when local numbering of narrowed parts
has been chosen.
Best regards, Marco
Thanks,
--
Marco
M-x org-lint in you Org file to check these
requirements (and more.)
HTH, Marco
node
Yes, I corrected this.
Ciao
--
Marco
ut (car ols) 'invisible t)))
(when (not (org-at-heading-p))
(outline-next-heading)
(defun mw-org-show-meta-info-lines ()
"Show meta info."
(interactive)
(mapc #'delete-overlay ols)
(setq ols nil)))
#+end_src
#v-
to completely get the proper
Hi Nicolas and all,
Is it just me or does
[[https://duckduckgo.com][DDG]]
show up now as
https://duckduckgo.com
with `org-link-descriptive' set to t?
I would instead expect
DDG
to appear. Wild guess: this is an issue in `org-activate-links'?
Ciao
--
Marco
is which is much less useable
>
> [1] https://somewebsiteaddress.net/path/to/page.do
> [2] id:eb1085ed-15fe-46a3-8b5e-3971587d1123
This sounds like a bug fixed a few days ago.
https://code.orgmode.org/bzg/org-mode/commit/b1429cdfe043b199bb7be6dc5c97a299954b4e0d
Can you check if the fix is in your copy of Org?
HTH, Marco
which is bound here to command org-open-at-point, on
the following heading opens the webpage as expected for commit
2b00d6281, b1429cdfe and f0dc3a06d.
#v+
* duckduckgo
[[http://duckduckgo.com][ddg]]
#v-
IOW I can't reproduce your issue AFAICS.
Is it a configuration issue?
Best regards, Marco
f the rest of the above docstring
>
>... while ‘org-ctrl-c-ctrl-c-hook’ is run before the first test.
>
> and add to this hook a function that recursively calls
> 'org-ctrl-c-ctrl-c before it does its own work - which seems
> incredibly kludgy.
Possibly it's a good idea to realize the implementation of your idea
independent of C-c C-c. And postpone the binding with C-c C-c.
HTH, ciao,
--
Marco
ist to discuss it
with people.
Ciao, Marco
tumashu writes:
> * lisp/org-agenda.el (org-agenda-breadcrumbs-separator): New variable.
> (org-agenda-format-item): Use org-agenda-breadcrumbs-separator
+1
Hi Marvin,
> Does anybody know how to view an animated gif as an inline video? I
> can see the first frame as an inline image, but I am unable to view
> the video.
{ M-x customize-variable RET org-file-apps RET }
opens my customization of variable org-file-apps which has the entry:
Hide Org Fil
>> Not sure what you mean. This is the problem, i.e., just this code
>>
>> #+begin_src emacs-lisp
>> (> 1 2)
>> #+end_src
>>
>> in an org file produces a parens mismatch, which, BTW, check-parens also
>> flags. Anywhere else (e.g., *scratch*) in Emacs this code produces no
>> mismatch.
> In an o
uot;)
- (modify-syntax-entry ?> ")<")
+ ;; (modify-syntax-entry ?< "(>")
+ ;; (modify-syntax-entry ?> ")<")
Up to now I don't miss the <> parenthesis. But this is just me.
Ciao,
--
Marco
syntax-entry ?> ".")
>
> as many of my org files have these symbols not as paren but as operators.
I'll follow your lead and add the lines
(add-hook
'org-mode-hook
(lambda ()
(modify-syntax-entry ?< ".")
(modify-syntax-entry ?> ".")))
to my config.
Thanks,
--
Marco
fo:org#The clock table]]
or even
[[info:org#The clock table]]
Ciao
--
Marco
ies my org files and I don't change blank lines by hand very
often any more.
What do you think about this? Is this worth to merge into org mode?
Ciao, Marco
P.S.: I have the code below in my init.el.
#v+
(defcustom org-style-blanklines-num-before-heading 1
"Number of blank lines
"[^\n]"))
(goto-char (1- (match-end 0)))
(when (looking-at "\\(\\(\t\\| \\)*\n\\)+")
(delete-region (match-beginning 0) (match-end 0)))
(insert numplusone-newlines
#v-
Ciao, Marco
ction org-bbdb-anniversaries-future can be found in the Org code and
BTW cooperates fine with BBDB AFAICT.
HTH, Marco
ing able to write lines like
#title: foo title
*anywhere* in the file to produce that title always astonished me.
Ciao, Marco
Hi Gustav and all,
Thanks for the refreshment of the org attach universe.
In particular I like the new attachment type for links. I'd like to
express my favorability to use the name "att" opposed to "attachment" to
specify that type.
Thanks for reading, best regards, Marco
ed subtree opposed to the previous version.
Of course I'm all for this change.
Is this worth to go into orgmode? What do you think?
Ciao,
--
Marco
>From add2614cf95d7ab569c95521747ec80f5eca2225 Mon Sep 17 00:00:00 2001
From: Marco Wahl
Date: Thu, 11 Jul 2019 12:08:47 +0200
Subject: [PATCH
Hi!
> I (ofc!) support this.
Thanks for your support!
I committed the stuff.
Ciao, Marco
in case it does not already exist?
What do you think?
Thanks and ciao, Marco
the star can be refined. But is it worth the
effort? Is there an issue apart from the cosmetic annoyance?
Ciao,
Marco
t the native scaling option as well
> when available. Since opting in to imagemagick will be Emacs wide and
> then we loose the benefit of the new functionality.
I committed a fix to the master branch. I think the way was clear. But
testing is welcome as always.
Thanks, Marco
ns in the 27 line.
Unfortunately I don't have a Mac and cannot examine the behavior you
describe AFAICS.
Hopefully a Org community member with access to a Mac can have a look.
Thanks for reporting,
--
Marco
ividual issue on Duan's side
AFAICT.
I highly recommend to blend out the individual configuration and try
again. If the display still fails then provide a concrete minimal
complete example for further invesigation.
Thanks all and best regards,
--
Marco
yed instead of LINK-TEXT (and LINK-TEXT goes unused:
> URL is still also given as the underlying link).
This was a little accident with the regexp match groups AFAICT. This is
fixed in master.
Thanks,
--
Marco
#+END_SRC
>> [...]
>>
>> produces a file with A and B in it. Expected: Just A. Changing
>>
>> #+BEGIN_SRC elisp :noweb-ref B
>> ;; B
>> #+END_SRC
>>
>> to
>>
>> # #+BEGIN_SRC elisp :noweb-ref B
>> # ;; B
>> # #+END_SRC
>>
>> does yield the expected result.
Your expectation looks right to me. I guess nobody thought about this
case before.
Happy hacking,
--
Marco
Zhengyu Duan writes:
> My image display problem was fixed with this commit
>
> https://github.com/hlissner/doom-emacs/commit/87b7a8da052601c51bc0577484916856364401cb
Thanks for the information!
Ciao,
--
Marco
Hi,
> This patch introduces a document level property drawer.
[...]
> What do you say?
I'll install the patch and have a look how it feels in my little
personal Org universe.
Thanks,
--
Marco
on between Org file and Org subtree should be kept
to a minimum. Wouldn't it be nice if Org files can be considered as Org
subtrees? In this sense a property drawer for the document is a step in
the right direction.
Ciao,
--
Marco
Adam Porter writes:
> Marco Wahl writes:
>
>> Adam Porter writes:
>>
>>> Gustav Wikström writes:
>>>
>>>> 3) Properties defined in a property drawer will have precedence over
>>>>properties defined as a property keyword, if
ing all operations and tools intact for
Org files not using the file wide property drawer AFAICS. If a tool
depends on a file wide property then it needs to be adapted. Possibly
this could be called "breaking" but I think this should not hold back
the proposal.
One could even think about letting fade out the "#+"-file-wide property
definition syntax or at least think about a good place within a file or
a subtree for those definitions. (There is at least Sebastian Miele who
wants to keep that syntax as he stated in another thread AFAIR.)
Personally I think it's a good idea to work for an Org mode where an Org
file behaves very much like an Org subtree.
Ciao,
--
Marco
Adam Porter writes:
> Marco Wahl writes:
>> You say the visibility is better for the #+-property keywords. I say
>> they can occur _anywhere_ in the file and even in some drawers. See
>> above "#+CATEGORY: cat-doc-prop-keyword-2".
>>
>> Further
Adam Porter writes:
> Marco Wahl writes:
>
>> One could even think about letting fade out the "#+"-file-wide
>> property definition syntax or at least think about a good place within
>> a file or a subtree for those definitions. (There is at least
>>
Gustav Wikström writes:
> I'd like to take the next step with this patch. I'm hesitant to do it
> without wider support though, since only a few people have commented.
>
> @Marco Wahl; As I understand you've applied the patch and tried it
> out. Have you found any
> subjective and may not represent my current picture of the "ideal".
> Nonetheless, maybe an interesting read for the ... other crazy people
> out there?
Okay, I'll have a look at your investigation. ;)
BTW this document looks great to me at the first glance.
Thanks,
--
Marco
e your case somewhat if you don't use master.
Ciao,
--
Marco
> Sooo, a separate branch is created in the Org mode repository named
> "next". I'm not entirely sure how we're supposed to work with it. But
> I've anyways pushed my (non-breaking) patch there.
Thanks again.
One issue for me is the positioning of the level 0 property drawer.
Having the requireme
ctation is not implemented. See function
org-read-date-get-relative.
+1 for someone trying to implement this idea.
HTH,
--
Marco
ossibilities
and the user is happy with fast parsing.
But I'm not 100% convinced that #+: lines should not be allowed before
the level 0 property drawer. E.g. #+title: in the first line looks nice
AFAICT.
> Happy to get more feedback on that decision though!
Hopefully some more feedback comes in...
Best regards,
--
Marco
agzam.ibragi...@gmail.com writes:
> While fooling around with capture templates, I have also noticed this:
>
> (progn
> (setq org-popup-calendar-for-date-prompt t)
> (read-date t)))
>
> When prompted, if you type something like "13:00" - it returns correct,
> expected datetime.
>
> But, if you
ian martins writes:
> Is it intentional that org-timer start, stop, and pause-or-continue all
> work from any buffer, but org-timer-set-timer only works from an org buffer?
I bet $1 that this is unintentional. If it was intentional this should
have been documented, I think. Possibly you are th
Jack Kamm writes:
> I've attached a patch which I believe fixes the issue.
Thanks.
> The problem appears to be that, when imagemagick is installed and the
> image width is unset, that the image will be created by an elisp
> expression like
>
> (create-file "some/image.png" 'imagemagick nil :wid
Soubzriquet writes:
> I'm new to using org-mode for time tracking, and have run into an odd issue
> with using "day" steps where the date is getting offset sometimes.
>
> I saw the issue with 26.1, was not fixed by updating to current
> environment with an empty init.el on OS X:
[...]
> * Day
2019-11-05 Tue]
>> > | Headline | Time |
>> > |--+|
>> > | *Total time* | *6:00* |
>> > |--+|
>> > | Day 6| 6:00 |
>> >
>> > #+END:
>>
>> I can not reproduce this behavior.
> Hi, sorry I was not more clear - the issue occurs also with emacs -Q or
> with empty init.el on my system.
Okay, thanks. I think I'm at the end of my abilities to investigate the
issue further.
I suggest you dig a little deeper for better understanding. E.g.:
- Try make the example of failure as small as you can.
- Check with a newer version of Org.
- Debug the issue.
Possibly someone else can confirm the issue.
HTH, Marco
nk your enhancement is great and worth a news entry. What about
pushing your code if nobody objects within one week?
Ciao, Marco
Hi Karl,
>>I think your enhancement is great and worth a news entry. What about
>>pushing your code if nobody objects within one week?
>
> Thanks, Marco; I'm glad you like it. I'll wait a week and then push
> (unless there's discussion, in which case
Karl Fogel writes:
> It allows you to choose what level subtree to narrow to. There are
> two ways to specify the subtree: use repeated C-u's to select "upward"
> from the current subtree, or use a direct numeric prefix arg to
> specify the subtree "downward" from level 1. (This is a somewhat
>
Karl Fogel writes:
> On 02 Dec 2019, Marco Wahl wrote:
>>What about numeric prefix arg 0 to reveal the whole buffer (aka
>>'widen')? I think this would be a logical completion to the feature.
>
> Since `widen' itself is already available via C-x n w, it migh
Terje Larsen writes:
> There is already org-image-actual-width but the problem with that one is
> that images that have quite small width, but are tall will be scaled and
> become very tall.
> I think it would make sense to introduce something like
> org-image-max-width, which would scale images
.
Please let me know if there are any issues with that change.
Thanks, Marco
Justin Vallon writes:
> When I use "emacs --no-init-file", I get the default distribution org
> packages, and " in my downloaded-melpa-install of org, it does not work.
>
> Distro org-version is 9.1.9, melpa is 9.3. describe-key TAB shows
> org-cycle, which is a kitchen-sink function. The docs
Tim Visher writes:
> On Thu, Dec 12, 2019 at 4:14 AM Marco Wahl wrote:
>
>> Justin Vallon writes:
>>
>> > When I use "emacs --no-init-file", I get the default distribution org
>> > packages, and "> > in my downloaded-melpa-install of org
gt; Any hints what is going wrong?
Possibly variable image-map is not used correctly in Org or should not
be used at all. The easiest fix would be to drop the usage of that
variable within Org, I guess.
Does the issue disappear when you do
M-: (require 'image) RET
before the image toggling?
Ciao,
Marco
stardiviner writes:
> I try to get the parsed HTML content into Org format content for org capture
> template.
>
> #+begin_src emacs-lisp
> (require 'org-eww)
> (with-temp-buffer
> (insert html)
> (org-eww-copy-for-org-mode)
> ;; FIXME does not yank converted content, inserted original HTML
Johannes Brauer writes:
> Typing C-c C-x C-v the image is displayed in the org buffer
> correctly. Typing C-c C-x C-v again the image does not disappear and I
> get the error message:
>
> org-toggle-inline-images: Symbol’s value as variable is void: image-map
>
> Any hints what is going wrong?
>
Allen Li writes:
> The command org-kill-note-or-show-branches bound to C-c C-k when used to
> show branches also expands headings tagged with :ARCHIVE:. This is
> contrary to expectations, as the manual states:
>
> ‘C-c C-k’ (‘outline-show-branches’)
> Expose all the headings of the subtree
Nicolas Goaziou writes:
> Hello,
>
> Marco Wahl writes:
>
>> A natural fix is committed, I think. Would be great if you could test
>> this fix.
>
> Thank you for the fix.
>
> Could you refactor it so belongs to org-compat.el? For example, we could
> crea
ct the whole file it would
be difficult or even impossible to give them reliable meaning for
subtrees AFAICS.
My 2ct,
--
Marco
> reference <>
You can find the answer in the documentation, I think. See e.g. (info
"(org) Noweb Reference Syntax").
HTH
--
Marco
Nuno Salgado writes:
> My question was to figure out what's the point to tangle the code
> without substituition!
Your imagination is the limit. E.g. this could be useful to document
the ":noweb eval" behavior opposed to ":noweb yes".
helps
me a bit and never got in my way. And I thought it would be quite
natural and consistent to use this binding for the agenda too.
What do you think about all that?
Best regards,
--
Marco
Bastien writes:
>> I've now tested this and see how it can be useful, but having C-c C-c
>> perform this unique deactivation in agenda view seems unfinished.
>
> Also, when columns are activated in an agenda view, org-columns-map
> already bind C-c C-c to org-columns-toggle-or-columns-quit, so C-
>> You miss the lines which have not been transformed into columns by
>> column view, and I think that's all.
>
> When I turn on `org-agenda-columns', all the lines of my agenda are
> transformed into columns. Can you give me an example where some lines
> are not transformed into columns? My ex
Bastien writes:
>> Thanks - I still don't see any real usecase.
>
> Ok, I constructed one:
>
> #+COLUMNS: %30ITEM %MYPROP
> #+PROPERTY: MYPROP_ALL "[x]" "[ ]"
>
> * NEXT Rien
> :PROPERTIES:
> :MYPROP: [ ]
> :END:
>
> In this case, when the cursor is on the MYPROP column in column
> (a
d not be possible to
> turn property drawers into non-special drawers by putting a #+ property
> before them. Now it is possible to sort of uncomment property drawers by
> putting #+ properties before them. This "feature" probably is hardly
> used, if at all.
I also think this is very corner case-y.
All in all I think your idea is good. But the masses did not scream for
that change so I think your idea is something for a wishlist to wait for
further discussion.
Best regards,
--
Marco
Hi Adam,
Adam Porter writes:
>> For some days now C-c C-c disables column view in Org files. This helps
>> me a bit and never got in my way. And I thought it would be quite
>> natural and consistent to use this binding for the agenda too.
>>
>> What do you thin
ew and org agenda restriction
> lock, but in my experience, those are less commonly accidentally
> activated.
I also think so for restriction lock.
Ciao,
--
Marco
also keep the original authors next to your name?
Best regards,
--
Marco
D writes:
> On 01.02.20 21:32, Marco Wahl wrote:
>> AFAICS org-bullets is released under GPL3. Doesn't this mean that you
>> can use org-bullets as a base for further development if you leave the
>> license intact and also keep the original authors next to your name?
&
> inserted time string taken into account).
>
> Marco, can you reproduce the problem in master?
I get back a date with a time in each case.
Concretely find the return values below if I do
C-u C-x C-e 11:55 RET
after each of the two sexp's below.
(progn
(setq org-popup-calendar
Dear all,
Up to now the text-scale of org columns sticks to one size disrespecting
text rescaling. (E.g. via C-x C-+ .)
I think this rigidity is unnecessary and I'd like to see org columns
follow text rescaling.
AFAICS the change is easy. (Just set `font' to nil in
`org-columns--display-here'.
Hi Bastien,
>> I think this rigidity is unnecessary and I'd like to see org columns
>> follow text rescaling.
>
> Agreed.
Fine!
>> AFAICS the change is easy. (Just set `font' to nil in
>> `org-columns--display-here'.)
>
> The change is a bit more complex, because you also need to adjust the
> s
Bastien writes:
> while Org 9.4 is on its way, I am considering changing a few default
> settings (10 options in total). I have created a survey here:
>
> https://framadate.org/Ufc42EVxS2jO1Ajz
>
> Can you take a few minutes and express your opinion there?
Ok. I'll go there in a minute.
> Her
;> * We have regular meetings with https://www.emacs-doctor.com/
>>
>> What are these meetings?
>
> We gather with fellow Emacsers in Paris once in a while.
Ahhh! Paris! Thanks for the information. Paris is out of my reach, though.
>From 49b00d2cf7ca4b8484e0a9679b39b62873ee30b6
Hi Bastien and all,
>> Subject: [PATCH 1/2] org: Fix corner case for org-kill-line
>>
>> * lisp/org.el (org-kill-line): Kill _all_ tags when the cursor is on the
>> tags part.
>
> There is a problem with this patch: when on a empty heading with tags,
> killing the tags will let the cursor back ri
en when no associated heading
can be identified (instead of erroring.) BTW this completely complies
with the docstring AFAICS.
Best regards,
-- Marco
Ian Garmaise writes:
> Thanks for that, it is indeed true that picking a heading is a workaround.
> I was confused because as far as I can tell there is no relationship
> between the countdown timer and any headline. I assume you mean the
> docstring for org-timer-set-timer, but maybe it is for
rther
configuration item to indicate that the dbus system shall be used.
Best,
-- Marco
-notification-handler #'message)
or add the line your init file.
AFAICS the condition with the dbus stuff is ignored if the handler is
set. In any case please report the outcome of your testing.
Thanks,
-- Marco
en in normal emacs,
> but not in org-mode. Is there a way to get this to work in org-mode?
> If this is a bad key combination for org-mode, I'm ok switching to
> another key combo.
What about using quoted-insert? C-q TAB
Ciao,
-- Marco
clearly how to implement this? (I don't.)
Best regards
Marco
pear with
`outline-show-children' -- e.g. properties and empty lines remain
hidden.
Cheers,
Marco
PC" . org-table-blank-field)
> ("C-c +" . org-table-sum)
> ("C-c =" . org-table-eval-formula)
> ("C-c `" . org-table-edit-field)
> ("C-#" . org-table-rotate-recalc-marks)
> ("C-c }" . org-table-toggle-coordinate-overlays)
> ("C-c {" . org-table-toggle-formula-debugger))
>
> Inspiration:
> http://endlessparentheses.com/define-context-aware-keys-in-emacs.html
Thanks!
Good to know a path to a personal configuration for the case no one else
is interested in the old C-c TAB behavior.
Ciao,
Marco
ing)
#+end_src
With branch
- wip-agenda-speedup
- master.
The overall outcome (from elp) was:
| wip-agenda-speedup | 823.31343007 |
| master | 13.70077639 |
Find details below.
HTH, Marco
I have 13 org-agenda-files.
*** wip-agenda-speedup
- first agenda creation
#+begin_src
are
| wip-agenda-speedup | 40.3 |
| master | 13.9 |
Details below.
Best regards, Marco
*** wip-agenda-speedup(f5bc563a6)
- first agenda creation
#+begin_src emacs-lisp :results drawer
(elp-instrument-package "org-")
(org-agenda-list)
(elp-results)
(set-buffer "*EL
p .:16:29.. test
.tmp .:16:30.. test
Pressing TAB in the agenda would jump to the respective plain list item.
Find the concrete patch below.
WDYT?
Best regards
Marco
--8<---cut here---start->8---
>From e2fd5f36b33e17063cf0
Nicolas Goaziou writes:
> Hello,
>
> Marco Wahl writes:
>
>> Let's say in an Org file you have the following plain list.
>>
>> * test
>>
>> - <2017-10-07 Sat 16:25> Start writing the RFC.
>> - <2017-10-07 Sat 16:29> Thought: &q
RET by default. I've
> happily been hitting return since 2008 to jump directly to timestamps.
> :)
:D
Thanks for the enlightenment!
Marco
;; I
> believe that there is no default binding.
There is. In an Org file
C-h w org-inlinetask-insert-task
yields typically the message
org-inlinetask-insert-task is on C-c C-x t
Regards
Marco
rg-agenda-switch-to-in-other-window)
--8<---cut here---end------->8---
into your emacs init file to get the the behavior you want with the key
C-u RET.
The function above is almost the same as `org-agenda-switch-to' which is
currently bound to RET in org agenda.
HTH
Marco
t (format "#+END_%s\n"
type))
(set-marker e nil)))
(org-defkey org-mode-map "\C-c\C-xw"'org-insert-structure-template)
#+END_SRC
2. In buffer *scratch* do
M-x eval-buffer
3. Voila! Check out C-c C-x w in an org mode buffer.
Best regards
Marco
.
Feel free to play with the implementation.
WDYT?
Should something like this enter orgmode?
Thanks for your time,
Marco
t;org-attach.el" instead of a new library.
I chose org-dired.el because of the similar gnus-dired.el from which the
idea has emerged. org-attach.el also looks like a good location for the
feature to me.
> Also, in the context of Org, an "org subtree" is simply a "subtree".
> I prefer "subtree" over "orgee".
Okay, I will stay with "subtree".
Thanks!
Marco
201 - 300 of 431 matches
Mail list logo
