n you reproduce this without your config file (i.e., by doing `emacs
-Q`)?
Because, indeed, that sounds really strange.
--
Cheers,
TRS-80
one else is affected/bothered by this?
I have been patching it locally, it would be nice not to have to manage
that any longer.
--
Cheers,
TRS-80
reventing this. See the
>> docstring of this option on how Org should catch invisible edits and
>> process them
>>
>
> org-fold-catch-invisible-edits does not exist in Org mode version 9.5.2,
> it should be org-catch-invisible-edits.
>
>
> thanks
> Jim Graf
Hi J
soon, vs. those I may truly never get to.
Anyway, just some food for thought.
--
Cheers,
TRS-80
le, above.
Let me know if you have any questions.
--
Cheers,
TRS-80
eading at the above site. YMMV of course.
--
Cheers,
TRS-80
> |
> #+END
>
> So a table is generated based on earlier entries.
>
> Is there the inverse operation? Given a table I recover the original
> properties?
I think it might be easier to do in awk than ELisp. And I am better in
Elisp than awk, but awk was made for almost
including some in Emacs (maybe even
within EMMS, if I am recalling correctly).
But then you can also access your music from outside Emacs, too. And
without needing to hack something up / re-invent the wheel in Org.
However, if you like to hack something up in Org instead, by all means,
continue!
ere is always the option of picking up maintenance yourself.
It often begins simply enough, fixing something that broke for
yourself... Next thing you know you are sharing those patches, before
you know it... you are suddenly maintaining a package. :)
Just some food for thought.
Cheers,
TRS-80
uments, it works quite well for
collaboration.
Unfortunately, HedgeDoc does not support Org Mode markdown, either. But
at least, in this case, thanks to F/LOSS, the possibility exists (at
least in theory) to add it.
Cheers,
TRS-80
[0] Even though I personally prefer Org over MD by quite a huge margin,
M
. :)
I already sync my Org Mode files (amongst other things) across all my
devices using Syncthing. I use git for plenty of other things, but not
for Org files. I edit them far too often, so I don't want to add any
friction to that process.
Cheers,
TRS-80
[0] No pun intended.
re! I even made an Info manual for my own
personal dotfiles repo! :D
Cheers,
TRS-80
[0] Try for yourself and see!
n
says above:
> Perhaps these limitations will be removed some day
Maybe they already have been? If not, worst case, I think you probably
learn more about what the problem might be.
Just a thought.
Cheers,
TRS-80
. No need for formula (which leaves more room for your own, should you
need it).
Just another way to do the same thing.
Cheers,
TRS-80
have a real
> modal editing, and that (in my case) would not be comfortable.
I agree with your assessment! In fact, I think I will give your
functions a try. Thanks for sharing them!
Cheers,
TRS-80
TRS-80 writes:
> On 2022-04-05 04:48, Karl Voit wrote:
>> Hi,
>> I've got following custom agenda for exporting:
>> | ("n" "no TODO events +180d"
>> | ((agenda "no TODO events +180d"
>> | ((org-agenda-span 180)
>>
Patches welcome? :)
Cheers,
TRS-80
Any ideas on that one?
I think you will need to write a custom ~org-agenda-skip-function~.
It's late and I am too tired, but if you are still floundering about
after some days, send another mail and I will see what I can do to help.
:)
Cheers,
TRS-80
On 2021-04-29 18:18, Samuel Wales wrote:
On 4/29/21, TRS-80 wrote:
My "quick and dirty" solution was to make a function to map over each
heading and assign a custom ID based on the text of the heading. It
only assigned one if one did not exist already (so in case you had
done
know if I got that from
Magit, general GNU/Linux usage, or what?
Having said that, I am not arguing in favor of OPs proposal. Just
mentioning the "single key" that came to mind, FWIW. As I mentioned
in another reply, I think things are fine the way they are. ¯\_(ツ)_/¯
Cheers,
TRS-80
options) so if I need the manual (or other information)
I go straight there. They each have their place, IMO.
Cheers,
TRS-80
ion! I look forward to circling back to it when I
have some time.
Cheers,
TRS-80
On 2021-04-28 00:03, Bastien wrote:
TRS-80 writes:
In the same timeframe, I have also noticed my Logbook entries not
being
indented (when changing TODO states) which I think was also brought
about by this change (or rather, my changes to org-adapt-indentation).
I am not sure if I should make
On 2021-04-28 00:09, Bastien wrote:
TRS-80 writes:
So, my reading of this new(?) headline-data setting, was that it
seemed
to be exactly what I had been looking for! But perhaps I
misunderstood?
So core idea behind (setq org-adapt-indentation 'headline-data) is to
let people end up
they would not be overwritten).
I had posted it very early in the thread, but it did not seem to gain
much interest. It was not posted as a "long term and proper solution
to be included into Orgmode" but rather a quick and easy workaround in
the meantime.
Cheers,
TRS-80
ppose it is an issue for this list.
Otherwise I don't think it is?
I guess there must be some reason you installed it from that
particular location?
Cheers,
TRS-80
If your expectations are slightly different to mine, hopefully there
is something in that thread that might be helpful for you.
Cheers,
TRS-80
ert 10:00
Expense I insert 10
And I obtain
| Bad template
What do I miss here?
Maybe try a minimal Emacs, just to make sure something else isn't
affecting it?
Cheers,
TRS-80
- I want to maintain lines in source that will match output
- in some other cases, too.
Really helpful!
Cheers,
TRS-80
t;)
"| %:fromname|%:fromaddress\n
%(my-extract-cc)|%^{Sheet|1|2|3|4|5|6}|%^{Exercise|1|} | %a|%:date |
" :prepend t
"| | %(my-extract-cc) | | | | | | || | | ||
| " :prepend t
)
But nothing worked, any ideas?
Thanks and regards
Uwe Brauer
Do you need to add more pipes to keep the table structure on the line
after the newline?
Cheers,
TRS-80
ntly evolves as my requirements and
priorities
change. It is and probably always will be, a work in progress!
I consider mine an ongoing experiment as well, which is why I have not
(as of yet) published anything. But I'm glad I decided to discuss it
on the list, as now I see I'm not the only one t
ould be called with point at each headline, so it would be easy to
map over a file or even a directory full of files, in order to
automate the archival process (perhaps annually?).
Cheers,
TRS-80
some notes and thoughts about
desired functionality and how it might work. And I keep monitoring
the mailing list for some better ideas. :)
Cheers,
TRS-80
e64 forums...
Cheers,
TRS-80
ction.
Luckily, Orgmode allows you to do that.
Cheers,
TRS-80
bit naive /
simplistic. Well, at least there is the option to create your own
archival function, which I suspect I will do at some point. In fact I
have been thinking about the best way to do that for some time
already.
Cheers,
TRS-80
On 2021-02-26 01:20, Kyle Meyer wrote:
TRS-80 writes:
On 2021-02-24 15:58, TRS-80 wrote:
On 2021-02-16 23:30, Kyle Meyer wrote:
[...]
So, if I'm reading your preferences correctly, it sounds like you
want
just the first suggestion in the above snippet, leaving
org-adapt-indentation at its
On 2021-02-24 15:58, TRS-80 wrote:
On 2021-02-16 23:30, Kyle Meyer wrote:
TRS-80 writes:
Unfortunately, unless I am doing something wrong, none of these
options
seem to really restore the previous behavior. I have set
~org-adapt-indentation~ to ~'headline-data~, and now pressing RET
goes
On 2021-02-16 23:30, Kyle Meyer wrote:
TRS-80 writes:
Unfortunately, unless I am doing something wrong, none of these
options
seem to really restore the previous behavior. I have set
~org-adapt-indentation~ to ~'headline-data~, and now pressing RET goes
to column 0. However, unfortunately
but a qualified path worked.
Could this be because of the symlink to my org directory? Is there a
better way to do it?
I do not use org-attach, but I do use a lot of symlinks (at the
underlying system level), and they never give me any trouble (for
whatever that's worth).
Cheers,
TRS-80
to
be completed. Therefore, try and make sure that org-log-into-drawer
gets called "last." I am pretty sure this will require digging into Org
internals to see in what order things go.
Sorry if that's vague, it's been a while since I dealt with this. And
it may or may not even actually be your problem.
Cheers,
TRS-80
/extremely/ annoying, and if I am being honest,
quite obnoxious behavior, which is the last thing I usually expect from
Emacs.
Cheers,
TRS-80
that might have put me off from
Orgmode /completely/ if I did not know how to quickly fix it.
For all of above reasons (and probably some others, too!), I do not
think this should be the default!
Please discuss.
Cheers,
TRS-80
, before starting to go down that path. Just my $0.02.
Cheers,
TRS-80
On 2021-01-12 15:33, Daniele Nicolodi wrote:
On 12/01/2021 21:21, TRS-80 wrote:
Hello *,
I just banged out a bit of Elisp implementing a new Orgmode link type
for navigating Ordered (i.e., numbered/lettered) Plain Lists.[0]
How do you deal with the lists being re-numbered when you edit them
de package?
Hence my thought to first float the idea on the mailing list.
I am also unsure I even like "plo:", maybe it should be "opl:" (for
Ordered Plain List)? Or even something else?
Discuss! :)
Cheers,
TRS-80
[0] https://orgmode.org/manual/Plain-Lists.html
On 2021-01-10 19:57, Kyle Meyer wrote:
Thanks for the initial report and the patch.
I am very happy to contribute!
Thanks for taking it easy on me the first time around. :)
TRS-80 writes:
Subject: [PATCH] org-footnote: fix inserting new footnote mangling
drawers
convention nit: s/fix
o/org/protocol/")
(require 'org-protocol)
El jue, 7 ene 2021 a las 8:17, Tom Gillespie ()
escribió:
It is built into the core org distribution.
Perhaps documentation should be updated?
Cheers,
TRS-80
On 2021-01-03 16:27, TRS-80 wrote:
Hello!
I seem to have come across a bug today in org-footnote.
I had just learned about the variable org-footnote-auto-adjust and set
it to t. Then I tried to test it by invoking org-footnote-new in my
Org file in between existing footnotes 2 and 3.
N.B
and cloned latest version and did a
diff on org-footnote.el between my affected version here locally and
latest, and the only change I saw was the copyright date.
So with that out of the way, I will start digging and see what I can
come up with.
Cheers,
TRS-80
Emacs : GNU Emacs 26.3 (build 2, x86_64
n, the water is fine... :)
Cheers,
TRS-80
[0] https://sr.ht/~trs-80/
On 2020-12-14 23:42, Ihor Radchenko wrote:
TRS-80 writes:
We are getting further and further afield from Orgmode discussion,
however I wanted to share the following article with anyone else who
followed this part of the thread all the way to this point:
Oops. Actually, hypothes.is
ow to annotate literally everything[0]
by karlicoss
There are quite a lot of other very interesting articles there as well
in the same (and related) veins. Enjoy!
Cheers,
TRS-80
[0] https://beepb00p.xyz/annotating.html
On 2020-12-12 23:57, pie...@caramail.com wrote:
TRS-80 wrote:
If you care to share a slightly bigger picture view, particularly
about the structure of the data you are trying to capture (and/or,
your workflow) we could likely come up with something that would work
much better for you than
n even use this to fill in Org Properties. Or you can use Org
Properties similar native completion, although by default that only uses
whatever values already exist in the buffer (which therefore could be
"none"), instead of your specified controlled vocabulary file as I used
above. I
o chose among large
number of items of anything.
This is much more along lines of what I had in mind. A nice simple
example of plain completing-read interface. However I am still not sure
that Org Properties are not the answer...
Cheers,
TRS-80
ning was trying to draw out relevent info, with the
end goal of suggesting the right solution. If that solution is a simple
completing-read then so be it but I am not even sure we have determined
that is the correct (or preferred) solution yet.
In particular, hash tables are not needed with the sorts of numbers of
candidates I think we are talking about here.
Cheers,
TRS-80
On 2020-12-12 22:49, pie...@caramail.com wrote:
TRS-80 wrote:
Are there any more to these templates you did not show?
Because, (and unless I am missing something) what I see are
essentially
all the same (and quite simple). You would end up with something like
the following in your target
when
org-enforce-todo-dependencies is non-nil?
Cheers,
TRS-80
particularly about
the structure of the data you are trying to capture (and/or, your
workflow) we could likely come up with something that would work much
better for you than a capture template, at least in this particular
case.
Cheers,
TRS-80
[0] https://github.com/Kungsgeten/yankpad
[1] https://orgmode.org/manual/Properties-and-Columns.html
expect you will be interested in that
conversation, as well.
Cheers,
TRS-80
On 2020-12-12 18:30, pie...@caramail.com wrote:
From: "TRS-80"
Well, it's up to you. If you want we can pursue either option, or
both
(one potentially as a temporary workaround). Or we can wait for more
list replies and see what others think. As I said there may also be a
bette
On 2020-12-12 17:46, pie...@caramail.com wrote:
From: "TRS-80"
The problem also exists when making capture templates. The solution
could be additional functionality coded in elisp that can then be used
for handling longer template entries. As the problem is dependent on
s
On 2020-12-12 16:51, TRS-80 wrote:
"If we are not in MAJOR-MODE, exit with error."
I noticed a small typo:
- "If we are not in MAJOR-MODE, exit with error."
+ "If we are not in major MODE, exit with error."
Cheers,
TRS-80
,
TRS-80
epted, etc... However in the
meantime...
With the above disclaimers out of the way, I present the following
function (and another simple one it depends on) in the hope they are
useful to someone.
[0] https://sourcehut.org
[1] https://sr.ht/~trs-80/
#+begin_src emacs-lisp
(defun my-major-mode-in
rification from OP which he was referring
to? Or what exactly trying to accomplish?
Cheers,
TRS-80
On 2020-12-11 11:48, steve-humphr...@gmx.com wrote:
TRS-80 wrote:
On 2020-12-11 10:45, steve-humphr...@gmx.com wrote:
>
> Incidentally, how can one print a list in messages buffer?
Do you mean something other than standard:
Correct, something other than "%s".
```
(mess
ges buffer, formatting them nicely. I use it when
debugging and writing code. However I am not sure that is what you are
looking for or not?
Cheers,
TRS-80
something Jean Louis is planning on
submitting as a patch to dired itself... ;)
Cheers,
TRS-80
.md, and then getting processed by Sourcehut's HTML renderer were
getting broken in the process. However now they are working, as can now
be seen for example at README of one of my projects:
https://sr.ht/~trs-80/rofi-in-elisp/
Please feel free to go there and click in-page links! In fact I can
nd project by having a
strong reaction to such negative attitudes.
Cheers,
TRS-80
ack to the
underlying project that generated the event on the agenda in the first
place. Becasue in my mind, I would jump from the agenda to the
underlying project or task and be making my notes in there directly.
Those linking considerations, in my mind anyway, would really dictate
the rest of the workflow.
Cheers,
TRS-80
On 2020-12-02 16:59, Tim Cross wrote:
TRS-80 writes:
I think the problem is actually because Sourcehut are sanitizing the
id
attribute out of links, as I have replied already to some other people
in this thread.
From what I can tell, yes your right. However, it also seems
On 2020-12-02 14:56, TRS-80 wrote:
On 2020-12-02 14:12, Jean Louis wrote:
Try using pandoc Org to Markdown as that could help until Org
exporting start working how it should.
Great minds must think alike! :) I tried that already but in-page
links
which look like:
```
[[*Setup][Setup
ay forward. As there
seem to be no good/clear (or at least, easy) answers.
Thanks for the input.
Cheers,
TRS-80
[0] https://karl-voit.at/2017/09/23/orgmode-as-markup-only/
On Wed, Dec 2, 2020 at 7:54 PM TRS-80
wrote:
Some further digging revealed that the ox-md exporter (which itself
is derived from the HTML exporter(?) makes extensive use of the id
attribute in links. And Sourcehut's HTML sanitizer only allows href
and title attributes (not id).[1]
[1] https
(or new) work to Markdown. I
really do hate Markdown that much. :D
Also, maybe in the meantime I could simply hard code a ToC, but that
still will not fix other in-page links throughout the page (like the
*Setup example, above).
Cheers,
TRS-80
[0] https://man.sr.ht/git.sr.ht/#setting-a-custom
been
some reason to do it that way in the first place.
So before I invest any more time going down this path, I thought I would
take a step back and seek some advice whether this is actually the
correct path or not?
Cheers,
TRS-80
[0]
https://lists.sr.ht/~sircmpwn/sr.ht-discuss/%3Cfe7aa296-9c90
feel about it.
Therefore, any stuff I plan on releasing publicly, I do not do in
literate style (JMHO). However if you are dead set on doing literate
paradigm, then maybe my experience is invalid for your use-case.
Cheers,
TRS-80
and a TAGS_META. The former for
general topics (i.e., computers, software, GNU/Linux, organization,
etc.), and the latter for things like BlogFodder, ReadingList,
NeedsCleanup, VideosToWatch, etc. which allows for a nice orthagonal
way to classify certain things.
TRS-80
.
Cheers!
TRS-80
I will
need to worry about that any time soon. ;) Even if so, it would be a
very
small implementation change anyway.
Cheers,
TRS-80
omfortable with some additional
reassurences that what I am planning is not some crazy or bad idea.
Thanks,
TRS-80
On 2020-09-10 18:00, Gustav Wikström wrote:
Hi TRS-80,
Your approach should work just fine. So fine, in fact, that it's
already kind of built in! Configure org-id-method and set it to 'ts
and you'll get timestamps as ID instead of uuid.
I do believe the manual lacks a description
icale already for a while.
Maybe you know all this already, I'm just adding my $0.02.
Cheers,
TRS-80
are referring to inside Emacs / Orgmode? I'm just
throwing out a possible alternative.
Cheers,
TRS-80
as mailing list
archive), but could not seem to reach a conclusive answer. I was hoping
that some more knowledgeable people could confirm
whether this is a really bad idea, or not. Any feedback would be
greatly appreciated!
Cheers!
TRS-80
[0] It could easily be extended to second (or further) resolution, if
needed. For me, minute resolution will be fine.
and method to reply (even
though I don't usually have problem on other lists).
Assuming I didn't overlook it, perhaps this is an opportunity to
improve said Docs?
Cheers,
TRS-80
, etc. high and low,
all
to no avail. So I decide to join the mailing list today. Probably long
overdue anyway. :)
Any tips would be greatly appreciated.
Cheers,
TRS-80
90 matches
Mail list logo
