:
> Hi Samuel,
>
> Samuel Wales writes:
>
>> i think it would be less error prone if we allowed c-u c-u to work
>> when adding a deadline to an entry. in maint it errors.
>
> Can you restate the detailed desired behavior vs. current behavior,
> and what
thank you. i think the problem needs specifying better than i specified it.
basically, i use org-refile for refile and goto, and i just want
exactly the same thing for inserting links also.
this is close to that other thread, but i want to emphasize that the
goal is specifically to merely use
ah, so org did the remap and i tried to remap the remap?
my brain is not working right now, but i think you might be right. in
either case, your solution works and is straightforward.
thank you.
On 8/21/20, Kyle Meyer wrote:
> Samuel Wales writes:
>
>> here is my code to try to
thanks. just wanted to make sure i wasn't supposed to report that it
wasn't working or was a different bug.
On 8/20/20, Nicolas Goaziou wrote:
> Hello,
>
> Samuel Wales writes:
>
>> i presume the fix will come out in the next release of maint?
>
> I applied t
i presume the fix will come out in the next release of maint?
[still getting in maint, which is ok; just confirming.]
On 8/16/20, Samuel Wales wrote:
> thank you both.
>
> On 8/16/20, Kyle Meyer wrote:
>> Nicolas Goaziou writes:
>>
>>> Yes, the problem lies in `o
i frequently use refile with ido to refile to and go to entries.
is there a command to use the same completion to insert a link at point?
for example, if i have an entry named pharmacy, and it has an org id,
i can refile to it or go to it using ido.
but can i be in an entry called whatever, and
thank you both.
On 8/16/20, Kyle Meyer wrote:
> Nicolas Goaziou writes:
>
>> Yes, the problem lies in `org-list-insert-item'. I pushed a fix and
>> a test for that.
>
> Great. Thank you!
>
--
The Kafka Pandemic
Please learn what misopathy is.
you know that thing in emacs where up to 20 self-insert-command
invocations are undone all at once? i dislike it and have fixed it
for everything except one command in org.
in org, backspace [org delete backward char] clusters for undo
["amalgamates" in emacs lingo] even when
thank you for looking into it.
recent maint on emacs 25.
i know this is an imperfect bug report with no mce that you can
probably repro. but perhaps it can trigger an idea that could lead
directly to a fix. my brain and computer limitations cannot do better
at this time.
when i run m-ret at the caret i get this bt. my
i recall wanting this at some point also, and also did not figure out
why one would not want it.
perhaps it thinks you will use an alternate to refiling if you know it
will be too slow.
but it's worth keeping in mind that caching has, or had, bugs. in
particular, if refile targets are filtered
i think the following boils down to:
i think it would be less error prone if we allowed c-u c-u to work
when adding a deadline to an entry. in maint it errors.
thank you.
On 7/22/20, Samuel Wales wrote:
> i tend to want either zero or some number [like 4 or 8] for deadline
> warnin
i tend to want either zero or some number [like 4 or 8] for deadline
warning days for deadline timestamps [tses].
so i set the deadline warning days variable to a nonzero positive
number as a default. and then manually add -0d to individual tses
when i want -0d.
however, manual editing feels
* look at /root and stuff
and see if it is similar to /tuber/
in recent maint this emphasises from /root to eoe.
dunno if it is feasible to fix, but there you have it.
thanks.
--
The Kafka Pandemic
What is misopathy?
in recent maint in emacs 25.
* x
asd fnjkasn dkfjan ksdjfn kajsdfn
^ajsdf kasdn kfjasnd jkfan ksdfn
* kill this whole header line and insert before caret
what i expect is that it is inserted above caret
what occurs is it gets inserted below
* z
this is surprising because i expected
l "n"] 3
nil nil] nil nil)
command-execute(#[0 "\300\301\302\"\207" [org-capture nil "n"] 3 nil nil])
so, user error, plus some anomaly.
however, if any ignorami like me exist out there, it might be worth
documenting int he warning screen that you should null the
On 6/29/20, Kyle Meyer wrote:
> would map to this (untested):
>
> ("b" . "src sh :results verbatim output")
thanks. i tried that too. it gave an error so i assumed it was
invalid syntax. should i report it as a bug?
On 6/29/20, Samuel Wales wrote:
> TAB or the new function, would bring up the warning which was not
> obviously fixable.
is not*
--
The Kafka Pandemic
What is misopathy?
https://thekafkapandemic.blogspot.com/2013/10/why-some-diseases-are-wronged.html
my understanding is that adding to org-modules and requiring are
functionally equivalent, at least in my use case.
for me, the problem is that expanding, whether via the familiar < q
TAB or the new function, would bring up the warning which was not
obviously fixable.
--
The Kafka Pandemic
What
quite frequent for me [most of the time], but i don't know what
triggers it. i am not able to narrow it down.
On 6/29/20, Nicolas Goaziou wrote:
> Hello,
>
> Samuel Wales writes:
>
>> i think it is worth pointing out a separate bug in case this code is
>> code is modi
i used to do
i think it is worth pointing out a separate bug in case this code is
code is modified.
with m-x org-insert-item or m-ret:
- zsdfasdfas
- asdfasdfa. asdfasdfasdf. asdfasdfasdfasdasd ,n ,mn
s,dfn ,amsdn f,a. |asdasdf,a sdfasd fsdnjkfanksda d.ssa
dkfasn df.
what i expect is this:
-
i keep wondering if this is similar to the idea of making all external
links cached. or specified ones. using a specified cache dir.
for example, you could have various external links in your
html-exportable document, and run a command to cache them all.
to clarify.
On 5/2/20, Samuel Wales wrote:
> there are a bunch of existing sort-of solutions, but to me the best is
> linking [as you mentioned], using org-id. although that only links to
> entries, and it requires following links. one entry becomes
> canonical. you have to
.
presumably org-id is the best solution for keeping track of which
files have or need virtual regions. basically an underneath layer of
org-id [but maybe not limited to entries] that the user does not
interact with.
On 5/2/20, Samuel Wales wrote:
> stating the obvious: org typically sto
stating the obvious: org typically stores a forest [files] of trees of
nodes. some things you want to put into it are best expressed more
generally than with trees. i call it [boring name] the tree problem.
there are a bunch of existing sort-of solutions, but to me the best is
linking [as you
i wonder if as a companion to such [perhaps hook-based user]
functionality, org-ellipsis could appear e.g. only if there is text
content.
i presume you've already tried -Q, but do you have anything like a
fill column marker package?
yes, it is a long shot.
On 3/24/20, Nathan Neff wrote:
> Hello all, I have had the 40th character missing
> from my agenda view, like this:
>
> Weeklytodo Expenses - Intern t and Friends
>
(call-interactively #'fill-region)
(fill-paragraph nil)))
On 3/16/20, Nicolas Goaziou wrote:
> Hello,
>
> Samuel Wales writes:
>
>> recent maint -- but i have not got an mwe. i could be doing something
>> wrong.
>>
>> * x
>> SCHEDULED: <2020-03-
recent maint -- but i have not got an mwe. i could be doing something wrong.
* x
SCHEDULED: <2020-03-15 Sun>
mada wakaranai to omou kedo, ima no meeru wa sono koto asdfa muri ni
suru kanosei ga aru.
if i fill that using m-x fill-paragraph, it fills the planning line also.
perhaps somebody
never mind. (time-to-days (float-time)) is sufficient.
On 3/3/20, Samuel Wales wrote:
> seems this used to work but does not now. what's a good replacement?
>
> (defun alpha-org-daynum-from-ts (ts)
> ;; internal time
> ;; (org-time-string-to-time "[2000-01-01]"
seems this used to work but does not now. what's a good replacement?
(defun alpha-org-daynum-from-ts (ts)
;; internal time
;; (org-time-string-to-time "[2000-01-01]")
;; (org-time-string-to-time "<2000-01-01>")
;; (org-time-string-to-time "")
(time-to-days (org-time-string-to-time
i have no right to respond as i have 483 scheduleds and 28 deadlines
and i get lost even trying to get one thing done per week, but i just
wanted to add to the advice so far.
there is org-edna for dependencies. org-depend also, but i think it
lacks the feature of scheduling a remote org-id
no opinion on anything but a suggestion.
i really like these little scripts that update your org files so they
are compatible with new org versions.
perhaps one can give them an argument or something to work on all
agenda files, or a list of files, or somethign liek that?
On 2/24/20, Bastien
interesting. i have often wanted blank lines between header and entry
content, but only if there is meta stuff there like drawers.
On 2/19/20, Adam Porter wrote:
> Hi Russell,
>
> This is not exactly what you asked for, but here's some code that
> ensures blank lines exist between headings and
recent org stackoverexchangeflowwhatgever post queries why <* is broken. :)
On 2/19/20, Bastien wrote:
> Hi Vladimir,
>
> Vladimir Lomov writes:
>
>>> I'm tempted to count the number of fingers involved ;)
>>
>> C-c C-, s --> Ctrl c , s
>> < s TAB --> Shift , s TAB
>>
>> ???
>
> I added the
in my old version at least, pretty entities talks about utf-8 and \name.
and the option under discussion does not mention pretty entitities.
dunno abou the implementation or any changes since my version,
but i am arguing from empiricism. the errors are all over the web. :)
On 2/19/20,
to stir the pot:
speaking for myself, i only wanted the output, and never the error
mechanism, and my attempts to get output reliably ended up in my
habitually putting in every shell block this boilerplate:
===
{
the code i actually want
} 2>&1
:
===
--
The Kafka Pandemic
What is misopathy?
just an idea but changing the subscript and superscript export feature
to ‘{}’ would reduce accidental invocation. i have seen solecistic
subscripts on websites created with org (probably by experts who
babelize their .emacs!), and on this ml :).
i have seen it used accidentally more than i have
On 2/19/20, Bastien wrote:
> - org-refile-use-cache => t
>
> This is a speed boost when refiling entries: if org-refile-targets
> is big, caching refile targets help refiling faster.
i predict this will generate bug reports.
in particular pay close attention to restricted refile and whether
On 2/16/20, Bastien wrote:
> I'm willing to spend as much time as needed on a MCE, but I'm waiting
> for this MCE before interpreting comments on code and possible bugs.
i see.
fyi i was not specifically trying to report a bug or supply an mce.
instead, i was hoping only to contribute to
i found a note that says that there isa nother disticnitont hat was
causing the bugs: a distinction between the current file and
non-current file.
it wreaks havoc to make that distinction.
* REF this works around the bugs
=this is in my personal patches
vvv
Modified
your quote is from a many years old report. i was providing it in
case it was useful historically.
--
The Kafka Pandemic
What is misopathy?
https://thekafkapandemic.blogspot.com/2013/10/why-some-diseases-are-wronged.html
non-leaf olpaths are not usefully considered to be directories in my
opinion. all olpaths should be equal in status.
On 2/16/20, Samuel Wales wrote:
> On 2/14/20, Bastien wrote:
>> What was the problem when refiling with ido?
>
> idk if the following will be useful but here
On 2/14/20, Bastien wrote:
> What was the problem when refiling with ido?
idk if the following will be useful but here goes.
bear in mind this was a while back. this is partly from memory.
i don't know if the fix fixed all of them, but it definitely seemed
to, at least with my ido settings.
again not sure if relevant and probably not, but it seemed to me that
the problem was related to something thinking that unix paths were
being completed, and directories were treated differently from
non-directories. whatever i did fixed it. took years to find and
fix.
dunno if this is useful (probably not), but i found the following was
necessary to fix ido. i didn't really understand it, but it fixed it.
Date: 2014-05-19 19:57:44 -0700
=== remove the parens from ido completion of olpaths
Modified lisp/org.el
diff --git a/lisp/org.el
istr an org-choice package that did somthin siilar with entries.
On 2/12/20, Bastien wrote:
> Hi Matus,
>
> Matus Goljer writes:
>
>> Thank you both for following up on this! I'm going to add a note to
>> my package that this feature is now built-in and deprecate it.
>
> You might want to wait
you probably already tried this to judge from your links but it's
worth poinitng out for mailing list readers that shell blocks use the
exit code. a user who just wants to run a diff or grep for the stdio
results (stderr and stdout) has to stop that mechanism.
if you want both stdin and stout,
On 2/10/20, Bastien wrote:
> Hi Samuel,
>
> thanks for your feedback.
>
> Samuel Wales writes:
>
>> obviously, as a default not indenting text as you seem to propose is
>> good for newcomers.
that statement was in the context of accessibility.
>
> Perha
i think this is a really good idea.
there are subtleties including:
- list bullets (fixed is good for aligning succeeding lines)
- timestamps (many align these informally or in headers)
- numbers (many align these informally -- but .,-+'?)
- todo kw (defined by user, would be fantastic
[this is addressed to bastien]
hi,
if you are thinking of changing the default to indenting meta lines
and asking for opinions on that:
fwiw, if org /were starting out/, i would propose that meta stuff not
be indented at all either. then the regexps everywhere could be
reliable. and it
hi bastien,
i deeply apologize. that statement was not clear. as much as
possible i will be more clear in the future. i appreciate your
looking into it.
nil has always worked for me. i didn't think a new feature was
necessary, but i am curious. what does your change do?
samuel
i have been using toc for an entire blog post and then
#+TOC: headlines 1 local
for sections.
this local idea is brilliant. i can make the main toc
non-intimidating, and then provide a toc for sections.
is it possible to do this automatically?
that is, supply only one main toc, and specify
should not have hit send on last email. meant to disengage
completely. will do so now. last email was not an invitation to
converse.
you do not know what every user needs.
On 2/4/20, Matthew Lundin wrote:
> and they are best addressed through add-on themes and packages.
agreed.
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
>&g
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.
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
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
fwiw i /think/ most of the rest of emacs makes c-c c-c
complete/send/do stuff with entered or modified text, while c-c c-k
cancels.
but we are not talking about cancelling edits so c-c c-k wouldn't be
quite right either.
i just know newcomers will want something. what is best idk.
[continuing from previous email and changing email header per
bastien's request to have separate threads/conversations per
suggestion.]
another useful change imo would be to allow categories to have their
own faces, selectable by regexp (so "^m-.*" could be yellow). similar
to tags and todo kw.
hi d,
On 2/1/20, Diego Zamboni wrote:
> I think you can configure most faces as you wish. For this, I have found
> the key "C-u C-x =" (which run what-cursor-position with the DETAILED
> argument enabled) very useful - among other things, it shows the face which
> is applied at the point under
org-table-header-line-mode?
hi texas,
apologies for any attribution errors.
headers in the agenda are on the right. so there is nothing to line
up except tags, which are also not lined up in the outline. so they
can be variable pitch ...
... unless you make headers line up with /one another/?
* like this
* and
i get the sense spacemacs has brought a lot of new users to emacs. i
don't use it but i have comments on your interesting and welcome
beauty tips.
i wasn't clear on the difference between beautifying list markers and
using org bullets.
this is really impressive. does it have a fill column?
i think it can be confusing to new users to have column mode
accidentally activated. what are the things they will try to get out
of it? maybe worth considering all the panic commands they'd try, and
either deactivate or message what to do to deactivate?
if c-c c-c is being weighed, maybe
i have been wondering about the search sequence for this
function.
id updating is capable of being quite slow, which can be distracting
when you follow a link and emacs hangs for a while, so i was thinking
maybe this could be optimized.
idk about data structures and searching, but i think the
hi,
On 1/20/20, Kyle Meyer wrote:
>> is isearch intended to be also affected? or just org-next-link? i
>
> No, isearch isn't affected.
thanks, that's a relief. then we have a "your life in plain text"
(i.e. matches everything) search inside emacs that will also work with
multi-buffer isearch
thanks from here too! interesting.
is isearch intended to be also affected? or just org-next-link? i
suppose isearch is a generic emacs thing, just as lgrep would be
generic, and most folk would want it to be generic and would get too
confused if it were not, but just want to make sure.
i
On 1/18/20, Jack Kamm wrote:
> What setting of org-src-window-setup are you using? If it is
> "current-window" or "reorganize-frame", this patch shouldn't affect you
> at all, as those implementations are left the same.
you're right, i have that set to current-window, as you might expect.
and it
i can't comment on your ideas at all, but just have one concern, which
maybe could trip up others like me. namely, pop-to-buffer, as stated
in its very docstring, prefers not the same window.
if i remember correctly, this is the window management problem i have
been struggling with since 2002.
dunno if this is useful but i encounter mangled visibility all the
time. concatenated headings and ellipsis at top of screen are the two
that i can think of that are most common. undo-tree might cause the
concatenated headings.
On 1/11/20, Nicolas Goaziou wrote:
> Hello,
>
> Miguel Morin
On 1/6/20, Fraga, Eric wrote:
> Tangling is for extracting code(s) from a document; exporting is for
> presentation or dissemination of that document.
actually i wasn't intending to ask for the difference. :) instead, i
was intending to say that i thuoght it was reasonable for a beginner
to be
On 1/5/20, Fraga, Eric wrote:
> Export and tangling are orthogonal to each other and are controlled
> independently by their respectively keywords in the src header
> lines. In other words, I am not sure I understand what one has to do
> with the other.
[fyi my computer broke some time ago and
i might be completely off on this, but it seems the problem is that
there is a corrupted buffer.
in particular, there is a missing newline at the end of the narrowed
region in the capture buffer. this causes the next header to join the
last line in the captured buffer.
i encountered this
at night, i need much more contrast in my emacs faces in order to
increase legibility.
during the day i want the same faces i currently have.
is it possible to programmatically increase foreground contrast
against their background in all faces?
i already have the background black or close to
sometimes i will get long lines pasted in from someplace.
all in a long set of lines
like this
except with longer lines
then i make it into a list.
but i want each item of the list to be filled.
so i make a region and fill and the items do not get filled.
sometimes filladapt works, but not
i think the biggest good thing about this is it's likely one of the
things users will try, after c-g and esc esc esc, to get out of this
really strange mode they accidentally got into.
On 12/5/19, Fraga, Eric wrote:
> Although I've not tried your enhancement yet, it is very welcome. Thank
>
to set to current file
(let ((org-refile-target-verify-function))
(let ((org-refile-targets '((nil . (:maxlevel . 50)
On 12/5/19, Samuel Wales wrote:
> for ido, i use ido-hacks which speeds ido and makes it work
> everywhere. then i use org-refile with the prefix arg that
for ido, i use ido-hacks which speeds ido and makes it work
everywhere. then i use org-refile with the prefix arg that makes it
do goto.
i also set a more restricted set of headers using refile and goto
tags, but org-refile probably does not recognize custom id.
On 12/4/19, Thibault Marin
[note: id markers use org ids.]
On 12/1/19, Samuel Wales wrote:
> i think it might be partlly a question of whether these numbers are
> fixed things that refer to fixed items [like referring to sections in
> a law that is not in the document] vs. being used to continue lists.
>
>
i think it might be partlly a question of whether these numbers are
fixed things that refer to fixed items [like referring to sections in
a law that is not in the document] vs. being used to continue lists.
they are both legitimate uses. in the first case, the @ syntax makes
sense to me, because
previous-buffer and next-buffer might be useful. emacs has oddities
here, so idk if it will work for you. i find that placing
(switch-to-buffer (current-buffer)), which you would think would be a
no-op, sometimes fixes those problems.
[there is also the emacs global mark ring, but htat has at
there is also pandoc, if you know something that you can export to
that pandoc can reasonably convert. like, who knows, html or
something.
this might be useful if you are in a hurry or you don't want to
install a non-distribution package or whatever.
On 11/10/19, Tim Cross wrote:
> This looks
the include route seems brittle to me, as you have to name the file
you are in. this would be interesting:
#+include: {{{input-file}}}::#yada-quote
(i have a bug in org more recent than a pretty old version so idk if
this is already possible.)
On 11/4/19, Richard Lawrence wrote:
> "Fraga,
i use comments, sometimes with self-highlighted /emphasis/ or
self-highlighted fixme, or demote to a standard "x" task and use tasks
one level above.
if it is exportable, then i use non-task entries as the thing to
export and do not export any tasks. this works pertty well.
on rare occasions i
ah, or do you mean you refer the reader to the text by a regular link
instaed of including? that's not what i am lokoing for here as these
are separate posts.
On 11/3/19, Samuel Wales wrote:
> can you give an example of using an internal link? this would work
> for me. but i am not g
can you give an example of using an internal link? this would work
for me. but i am not getting what you mean.
* text to be included
<>
* blog post 1
twinkle star [syntactic magic]
?
On 11/3/19, Fraga, Eric wrote:
> I use macros generally for this. For longer bits of text, I reword and,
>
org has a bunch of mechanisms for included text, including macros, the
include statement, and maybe babel.
i want to take some text and stick it in a paragraph in a few
subtrees, but have it be in a single entry.
so like:
===
* my insertable text
alpha, beta, gamma
* one blog post
whatever
the following will not work for you due to dependencies.
has worked for me for many years.
puts ! in agenda prefix if schedule or deadline. if it is agenda
agenda [timestamp agenda, daily/weekly agenda] it requires closed
also.
(with-eval-after-load 'org-agenda
;; bangify agenda prefix
continuing one after prev list is a great idea. then you won't get
out of sync. dunno if feasible.
--
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
not sure if that works in gmail, however. maybe it's possible to add
an "o" tag [or whatever gmail calls it], but i'm not sure if there is
a complete and reliable header parser.
On 10/31/19, adam wrote:
>
> Thanks. Just found that now.
>
>
>
>
>
--
The Kafka Pandemic
What is misopathy?
beware # at eob with no newline.
On 10/27/19, Adam Porter wrote:
> I agree with Robert that "whitespace" includes newlines in "Emacsland."
> For example, with this document (the second "#" has a newline
> immediately after, no spaces or tabs):
>
> #+BEGIN_SRC org
> foo
>
> # comment
>
> bar
>
>
i have an outdated version of org, so this might have been fixed, but
it is an old bug.
cycling a trivial entry with text in it seems to have 2 states.
cycling the entry with a list in it seems to have 3 states.
i expect both to have 2 states, unless a variable is set to cycle
lists or it is a
i don't use the priority stuff, but i think it could perhaps be useful
to use terminology to distinguish the priority stuff from
the priority stuff.
i.e.
1] the stuff i don't use that you are talking about
2] [#A] and all that
when i was a beginner i got confused by that.
:)
On 10/9/19, Adam
i keep each blog entry in a subtree. then i export to html. then i
paste into blogger. done.
maybe not helpful, but maybe somebody will chuckle?
--
The Kafka Pandemic
What is misopathy?
https://thekafkapandemic.blogspot.com/2013/10/why-some-diseases-are-wronged.html
The disease DOES
thanks for your clarification. i had thought that it did the
daily/weekly agenda also. that's the one that is slow for me.
On 9/7/19, Adam Porter wrote:
> Samuel Wales writes:
>
>> i was merely trying to get a sense of the degree to which it is a
>> drop-in replacement
On 8/30/19, Adam Porter wrote:
>> also, does it support all the usual variables for leaders and faces and so
>> on?
>
> I'm not sure exactly what you mean. Formatting of entries is not
i was merely trying to get a sense of the degree to which it is a
drop-in replacement (which i think you have
501 - 600 of 2167 matches
Mail list logo