Re: I can't set dabbrev to respect the writen case

2022-05-15 Thread Samuel Wales
i do not use fancy-dabbrev, but i use dabbrev in hippie-expand.  it
seems to do as you want.

it should be possible to run hippie-expand with just dabbrev.  it
might not be exactly the same because he might have its own version of
dabbrev.  which might be what you want in this case.

note that you have control over where dabbrev gets its data.  idk if
that is a feature of vanilla dabbrev.

i do not use any dabbrev settings or any he settings except the main
one for he.  it is set to

  '(try-expand-dabbrev-visible
try-expand-dabbrev
try-expand-dabbrev-all-buffers
try-expand-dabbrev-from-kill

try-complete-lisp-symbol
;;do i want this first?  am i supposed to use another thing to
;;complete from that point?
;;try-complete-lisp-symbol-partially

;;try-expand-whole-kill
try-complete-file-name-partially
try-complete-file-name
hoka-try-complete-with-calc-result)


On 5/14/22, Ypo  wrote:
> Hi
>
> I find dabbrev and fancy-dabbrev very useful to typing fast. But there
> is a problem I am not able to solve: When I apply an expansion while
> writing, the case is always that of the expansion, I can't make it to
> respect what I have written. An example:
>
> — (Typing) "Hel
>
> — (Offered expansion) "hello"
>
> — (What I get when accepting the expansion) "hello"
>
> — (What I wanted) "Hello"
>
>
> Best regards,
>
> Ypo
>


-- 
The Kafka Pandemic

A blog about science, health, human rights, and misopathy:
https://thekafkapandemic.blogspot.com



Re: org-fold documentation

2022-05-06 Thread Samuel Wales
so one would not be able to load all of org then compile?

On 5/6/22, Ihor Radchenko  wrote:
> Samuel Wales  writes:
>
>> is there a quick trick like loading everything first?  for .el under
>> my control i have a[n otherwise] strict policy of clean compilation
>> but don't declare.  just load before compiling.
>
> I am not aware about such trick. native-comp works in isolated Emacs
> process for each individual .el file.
>
> Properly resolving the warning on Org side is impossible because we rely
> on runtime. Putting all the necessary requires would cause circular
> requires :(
>
> Best,
> Ihor
>


-- 
The Kafka Pandemic

A blog about science, health, human rights, and misopathy:
https://thekafkapandemic.blogspot.com



Re: org-fold documentation

2022-05-06 Thread Samuel Wales
is there a quick trick like loading everything first?  for .el under
my control i have a[n otherwise] strict policy of clean compilation
but don't declare.  just load before compiling.

not using native yet so idk if the q makes sense.


On 5/6/22, Ihor Radchenko  wrote:
> Vikas Rawal  writes:
>
>> After upgrading to 9.5.3, I am getting warnings such as this, which I
>> suspect are due to org-fold.et.
>>
>> Warning (comp): org-fold.el:834:27: Warning: Unused lexical variable
>> `org-hide-macro-markers' Disable showing Disable logging
>> Warning (comp): org.el:76:30: Warning: Package cl is deprecated Disable
>> showing Disable logging
>> Warning (comp): ox.el:79:1: Warning: the function ‘org-back-to-heading’
>> might not be defined at runtime. Disable showing Disable logging
>> Warning (comp): ox.el:79:1: Warning: the function
>> ‘org-next-visible-heading’ might not be defined at runtime. Disable
>> showing
>> Disable logging
>> Warning (comp): ox.el:79:1: Warning: the function ‘org-at-heading-p’
>> might
>> not be defined at runtime. Disable showing Disable logging
>>
>> Is org-fold.el documented already? Any pointers to what might be causing
>> the above?
>
> These are native-comp warnings. They are not uncommon when
> native-compiling Org (not only org-fold.el) and generally harmless.
> If you are sufficiently annoyed with them, most of these warnings can be
> "fixed" by declaring the missing functions. The functions are available
> at runtime, but not during native-compilation.
>
> Best,
> Ihor
>
>


-- 
The Kafka Pandemic

A blog about science, health, human rights, and misopathy:
https://thekafkapandemic.blogspot.com



[tip] direct specification of deadline warning days without editing text

2022-05-04 Thread Samuel Wales
in retrospect this solution is completely obvious but i thought i
would mention it in case somebody searches for it.

in agenda, i do c-u c-u c-d.  this allows me to remove deadline
warning days [RET, very convenient!] or specify them.

a good thing about this feature is that there is less chance of
manually creating a format error in the timestamp as would occur by
going to the ts and editing it manually.  also it seems nothing is
relative to the existing warning.  that is good.

the prompt, however, seems geared toward specifying a date.  you can
specify indirectly the deadline warning days by specifying the date
that would be the warning.  the question is, can we specify deadline
warning days directly?

here is where it is obvious in retrospect but as i was not thinking in
terms of default date it was not.

suppose i want deadline warning days of -2d but do not want to
manually edit the ts or calculate the corresponding date.

if the deadline is somewhat in the future but displayed in the
deadline section of the agenda, and i try c-u c-u c-d, the following
intuitive ideas do not work: 2, -2, 2d, -2d, and as desperation,
trying the in retrospect nonsensical . first.

i wasn't fully cogitating that the prompt was date oriented but that
the default date is the ts date and can work.

i read the manual for my obsolete version of org (info "(org) The
date/time prompt") and my brain did not find it.  i was looking at the
examples for things like -- even though they were mentioned in the
text.

solution seems to be --2d.  whether modern org needs to include a few
examples with -- or not, idk.

idk if that helps anybody [it is going to take much time to upgrade].



Re: [BUG] - Statistics cookie is part of the org heading title

2022-05-03 Thread Samuel Wales
some code removes it.  for example creating a link to a headline using capture.

On 5/3/22, Daniel Fleischer  wrote:
> Fabian  writes:
>
>> I don't see any reason why the statistics cookie should be part of the
>> title: it should be a separate component.
>
> According to the spec, the statistics cookie can appear anywhere, it's a
> text element. It can appear in a headline where it has more meaning and
> also appear anywhere in the headline, not necessarily at the end. The
> function you failed to mention but is mentioned in the link is
> `org-heading-components` which does a simple split around syntax parts:
> stars, TODO word, text, tags. If you don't want to see the cookie you
> can remove it easily from text using regex.
>
> --
>
> Daniel Fleischer
>
>


-- 
The Kafka Pandemic

A blog about science, health, human rights, and misopathy:
https://thekafkapandemic.blogspot.com



Re: [Bug] incorrect indent of next heading after org-paste-subtree

2022-05-02 Thread Samuel Wales
that sounds like great debugging ability.  was this using edebug or something?



Re: Emacs launched from Firefox

2022-05-01 Thread Samuel Wales
thank you.  there is no emacs in my ~/.config/mimeapps.list.  where
are those desktop files found or put?  i use fluxbox.
[i realize this is not org related.  non-list email ok.]


On 5/1/22, Max Nikulin  wrote:
> On 01/05/2022 11:53, Samuel Wales wrote:
>>
>> [firefox did not offer to allow a command line to run my shell script
>> which sets up emacs correctly, and idk if it even ran with my .emacs.
>> does it do -q?  not sure because emacs is too unusable to even find
>> that out.  so firefox fails to be accessible in that dialog box.
>
> Samuel, I think, firefox does exactly what it can find in MIME
> associations (e.g. ~/.config/mimeapps.list) and in the .desktop file of
> the selected application.
>
> There is an emacsclient.desktop file in Emacs git master that tries to
> connect to the existing Emacs session. It is a relatively new addition,
> so packages for Linux distributions may miss it.
>
> You can either use standard Emacs initialization to get all your
> customization available through default emacs.desktop or create a custom
> .desktop file that contain all CLI options specific to your setup.
>
>
>


-- 
The Kafka Pandemic

A blog about science, health, human rights, and misopathy:
https://thekafkapandemic.blogspot.com



Re: [Bug] incorrect indent of next heading after org-paste-subtree

2022-05-01 Thread Samuel Wales
fwiw
[idk if this is useful but here just in case]

iirc, outline mode does not include the final newline for subtrees in
at least one case.

yet, many users and much code assume or ensure that lines are
terminated with a final newline.

this can result in unexpected behavior.  it required code to ensure
compatibility and flexibility, and it required consideration for edge
cases.  sometimes the workarounds would have to be worked around by
the calling code.

core emacs code like sorting assumed/assumes newline.

org would assume or provide none in some [but not all] cases.

user or package code might naturally kill a subtree by killing the
whole line when folded or killing each of the lines.  those include
final newline.  or set require-final-newline.  this is anissue for
things similar to editing source blocks or capture.

the usual bugs were unexpected presence or absence of newlines.  idk
if htat might help you debug or not.


On 11/30/21, Max Nikulin  wrote:
> Another old bug with org-paste-subtree.
>
> It make indentation of next heading wrong.
>
> Consider the following document and follow described steps:
>
>  >8 
> #+STARTUP: indent
> Enable soft indent mode
>
> Put to kill ring some text *without trailing newline*
> that represents a subtree. In my case it is generated
> by a browser extension.
> #+begin_src elisp :results silent
>(kill-new "* Pasted Header\nPasted body")
> #+end_src
>
> Several levels of heading to make the problem apparent:
> * H1
> ** H2
> Ensure that the following "H3" heading is expanded,
> put cursor to this line and try =C-c C-x C-y=
> or [[elisp:(org-paste-subtree)]]
> *** H3
> :PROPERTIES:
> :CUSTOM_ID: h3
> :END:
> Body
>  8< 
>
> Actual result:
>
>  >8 
> Several levels of heading to make the problem apparent:
> * H1
> *** H2
>  Ensure that the following "H3" heading is expanded,
>  put cursor to this line and try =C-c C-x C-y=
>  or elisp:(org-paste-subtree)
> * Pasted Header
>Pasted body
> * H3
>:PROPERTIES:
>:CUSTOM_ID: h3
>:END:
>Body
>  8< 
>
> Expected result
>
>  >8 
> Several levels of heading to make the problem apparent:
> * H1
> *** H2
>  Ensure that the following "H3" heading is expanded,
>  put cursor to this line and try =C-c C-x C-y=
>  or elisp:(org-paste-subtree)
> * Pasted Header
>Pasted body
> * H3
>:PROPERTIES:
>:CUSTOM_ID: h3
>:END:
>Body
>  8< 
>
> Org mode version 9.5 (release_9.5-225-g494c20
>
>
>


-- 
The Kafka Pandemic

A blog about science, health, human rights, and misopathy:
https://thekafkapandemic.blogspot.com



Re: [PATCH] Add make target to ease creating reproducers and testing them

2022-04-30 Thread Samuel Wales
i took another look.

repro args might be enough for most users.

> As for accessibility, I doubt that we can provide something that fits all 
> people. Not to mention that accessibility settings themselves can
affect reproducer.

i don't think anybody is asking for the first point.  if something is
unusable at all, it won't be reproed, so the second point is sort of,
either it gets reported along with the settings as a heads up, or it
doesn't get reproed.


On 4/30/22, Samuel Wales  wrote:
> thanks for reply.  merely pointing out that: some users, myself
> included, need settings to make the system work at all.  that is, it
> is impossible to use emacs.  this is solved in some cases by .emacs
> settings and command line args.
>
> for example, just today i clicked on a download link --- for your
> patch, now that i think about it --- and firefox suggested emacs as an
> alternative to saving.  so i tried it, and emacs came up completely
> unusable.  i was able to save using the firefox dialog box, then open
> with my regular emacs, but wasn't able to determine much from the
> patch in my case.
>
> [firefox did not offer to allow a command line to run my shell script
> which sets up emacs correctly, and idk if it even ran with my .emacs.
> does it do -q?  not sure because emacs is too unusable to even find
> that out.  so firefox fails to be accessible in that dialog box.  they
> probably never thought anybody would need to run a command line
> instead of choosing from some "applications" list.  whereas i never
> thought major free software would /not/ provide for a command line.
> different perspective i guess.]
>
> if those users are not anticpated by the make target, perhaps a line
> indicating something like that [idk what as i didn't understand the
> patch] in the description would be useful so that they do not have to
> follow a false trail?
>
>
> On 4/30/22, Ihor Radchenko  wrote:
>> Samuel Wales  writes:
>>
>>> coupld of questions.  first, is there accommodation for accessibility?
>>>  e.g. if a user needs a setting for large fonts, small window size to
>>> not be larger than monitor size, any emacs args, black bg.
>>
>> There is REPRO_ARGS variable. It can be used to pass any extra args to
>> Emacs. I provided relevant example in the manual (see the patch).
>>
>> As for accessibility, I doubt that we can provide something that fits
>> all people. Not to mention that accessibility settings themselves can
>> affect reproducer.
>>
>>> for these reasons, and because setup of agenda etc. takes a bit of
>>> code, my test file is not tiny.  but maybe it is good enough to
>>> combine user setup with the code that triggers the issue.  for
>>> simplicity.  [in my case by variations i mean e.g. which version of
>>> emacs, which version of org, whether my .emacs is loaded.  i doubt
>>> this is needed, but some users might want to set such things sometimes
>>> for comparison.  probably simplicity should be a higher priority.]
>>
>> We cannot expect users to do anything more than reporting their system,
>> Emacs, and Org mode versions. If desired, our Makefile provides EMACS
>> variable to control which Emacs executable to use.
>>
>>> second, this is for which instantiations of org?  git yes, what about
>>> package managers?  built-in org??
>>
>> This is for git and assumes that git version of Org is already
>> downloaded (how would you run make repro otherwise?).
>>
>> For built-in Org, manual just says emacs -Q. Nothing much to simplify.
>> For package managers, users need to provide the load-path. Again,
>> details are already covered in the manual.
>>
>> Best,
>> Ihor
>>
>
>
> --
> The Kafka Pandemic
>
> A blog about science, health, human rights, and misopathy:
> https://thekafkapandemic.blogspot.com
>


-- 
The Kafka Pandemic

A blog about science, health, human rights, and misopathy:
https://thekafkapandemic.blogspot.com



Re: [PATCH] Add make target to ease creating reproducers and testing them

2022-04-30 Thread Samuel Wales
thanks for reply.  merely pointing out that: some users, myself
included, need settings to make the system work at all.  that is, it
is impossible to use emacs.  this is solved in some cases by .emacs
settings and command line args.

for example, just today i clicked on a download link --- for your
patch, now that i think about it --- and firefox suggested emacs as an
alternative to saving.  so i tried it, and emacs came up completely
unusable.  i was able to save using the firefox dialog box, then open
with my regular emacs, but wasn't able to determine much from the
patch in my case.

[firefox did not offer to allow a command line to run my shell script
which sets up emacs correctly, and idk if it even ran with my .emacs.
does it do -q?  not sure because emacs is too unusable to even find
that out.  so firefox fails to be accessible in that dialog box.  they
probably never thought anybody would need to run a command line
instead of choosing from some "applications" list.  whereas i never
thought major free software would /not/ provide for a command line.
different perspective i guess.]

if those users are not anticpated by the make target, perhaps a line
indicating something like that [idk what as i didn't understand the
patch] in the description would be useful so that they do not have to
follow a false trail?


On 4/30/22, Ihor Radchenko  wrote:
> Samuel Wales  writes:
>
>> coupld of questions.  first, is there accommodation for accessibility?
>>  e.g. if a user needs a setting for large fonts, small window size to
>> not be larger than monitor size, any emacs args, black bg.
>
> There is REPRO_ARGS variable. It can be used to pass any extra args to
> Emacs. I provided relevant example in the manual (see the patch).
>
> As for accessibility, I doubt that we can provide something that fits
> all people. Not to mention that accessibility settings themselves can
> affect reproducer.
>
>> for these reasons, and because setup of agenda etc. takes a bit of
>> code, my test file is not tiny.  but maybe it is good enough to
>> combine user setup with the code that triggers the issue.  for
>> simplicity.  [in my case by variations i mean e.g. which version of
>> emacs, which version of org, whether my .emacs is loaded.  i doubt
>> this is needed, but some users might want to set such things sometimes
>> for comparison.  probably simplicity should be a higher priority.]
>
> We cannot expect users to do anything more than reporting their system,
> Emacs, and Org mode versions. If desired, our Makefile provides EMACS
> variable to control which Emacs executable to use.
>
>> second, this is for which instantiations of org?  git yes, what about
>> package managers?  built-in org??
>
> This is for git and assumes that git version of Org is already
> downloaded (how would you run make repro otherwise?).
>
> For built-in Org, manual just says emacs -Q. Nothing much to simplify.
> For package managers, users need to provide the load-path. Again,
> details are already covered in the manual.
>
> Best,
> Ihor
>


-- 
The Kafka Pandemic

A blog about science, health, human rights, and misopathy:
https://thekafkapandemic.blogspot.com



Re: [PATCH] Add make target to ease creating reproducers and testing them

2022-04-30 Thread Samuel Wales
quicker repro is a great idea.  long ago i created a test file that
serves a similar purpose and some shell functions for variations.  i
have to try to reacquaint with all of that each time, which can be
enough of a barrier to not repro.

coupld of questions.  first, is there accommodation for accessibility?
 e.g. if a user needs a setting for large fonts, small window size to
not be larger than monitor size, any emacs args, black bg.

for these reasons, and because setup of agenda etc. takes a bit of
code, my test file is not tiny.  but maybe it is good enough to
combine user setup with the code that triggers the issue.  for
simplicity.  [in my case by variations i mean e.g. which version of
emacs, which version of org, whether my .emacs is loaded.  i doubt
this is needed, but some users might want to set such things sometimes
for comparison.  probably simplicity should be a higher priority.]

second, this is for which instantiations of org?  git yes, what about
package managers?  built-in org??


On 4/30/22, Ihor Radchenko  wrote:
> Hi,
>
> In the Feedback section of the manual, we provide instructions on how to
> create reproducers: https://orgmode.org/manual/Feedback.html
>
> The instructions are nice, but I was thinking to simplify things for the
> users further.
>
> I propose a new make target: make repro
> It will run the commands we already suggest, but without a need to
> create minimal file, pass all that arguments to emacs, etc
>
> WDYT?
>
> Best,
> Ihor
>
>


-- 
The Kafka Pandemic

A blog about science, health, human rights, and misopathy:
https://thekafkapandemic.blogspot.com



Re: Automatically use Heading Content as EXPORT_FILE_NAME?

2022-04-26 Thread Samuel Wales
fwiw, what i do is export to a buffer, then write to a file whose name
is derived from the header.

(alpha-make-valid-path
(with-current-buffer org-buffer
(org-get-heading 'no-tags 'no-todo)))

(defun alpha-make-valid-path (s)
  "Make a string into a filesystem path."
  ;; see files.el for this and tramp
  (subst-char-in-string ?/ ?!
 (replace-regexp-in-string "!" "!!" s)))

i think it might have some issues with long headers and some basename
limit on linux.  you seem to truncate for that.


On 4/26/22, Tim Visher  wrote:
> On Tue, Apr 26, 2022 at 11:54 AM Tim Visher  wrote:
>
>> I'm currently going to hack around it I think by simply making a function
>> that updates the EXPORT_FILE_NAME property with the current heading text.
>>
>
> That's something like
>
> ```
> (defun timvisher-org-set-export_file_name-property-to-heading-text
> ()
>   (interactive)
>   (org-set-property
>"EXPORT_FILE_NAME"
>(let ((stripped-heading
>   (replace-regexp-in-string
>"[^-A-Za-z0-9_.~#+ ]"
>""
>(substring-no-properties (org-get-heading t t t t)
>  (substring-no-properties
>   stripped-heading
>   0
>   (min (length stripped-heading) 250)
> ```
>


-- 
The Kafka Pandemic

A blog about science, health, human rights, and misopathy:
https://thekafkapandemic.blogspot.com



Re: org-agenda todos list sorted by earliest deadline first

2022-04-02 Thread Samuel Wales
perhaps try including your code and the emacs and org versins.  i
think there have been recentish changes insorting strategy.

might also try paradoxically deadline-down etc.

On 4/2/22, Sébastien Gendre  wrote:
> Hello.
>
> In org-agenda, for the todos list, I try to have tasks with deadlines at
> top. With earliest deadline first.
>
> But, when I customize the variable "org-agenda-sorting-strategy" by adding
> "deadline-up" for "todo" and "tags", it has no effect.
>
> Any advice ?


-- 
The Kafka Pandemic

A blog about science, health, human rights, and misopathy:
https://thekafkapandemic.blogspot.com



Re: Drop defadvice from Org

2022-04-01 Thread Samuel Wales
On 3/31/22, Stefan Monnier  wrote:
> I definitely hope it will be gone before 2040, but it hasn't even been
> declared officially obsolete yet (not even in `master`), so I think you
> should be good at least until 2030.

thanks.

i was ok with the scold for a long time about (` thing but my reactin
time slowed significantly and that was trivial-er.

2040 is when i will begin figuring out or finding some long lost
convert thing, and then decide to do something about my carefully
self-cargo-culted advice.  fortunately, debian on the trailing edge
will give me a bit more.

still trying to get my scripts to understand the new branch names.



yanking into body text ends up after the entry

2022-04-01 Thread Samuel Wales
imagine this

* to yank
a
b
c
* x
^sadfsadf
^^*** y

if i kill the to yank entry, then paste at ^,it ends up at ^^ instead.
this is logical in that to yank would swallow the body text, but i am
wondering when this behavior started.

when i kill to yank as a shortcut for moving its body text, my
intention is to kill the header afterward. and so the behavior, is
surprising.  idk a command for "kill header and copy body".

if that makes any sense.



Re: Drop defadvice from Org

2022-03-31 Thread Samuel Wales
thank you.  just an idle question.  is it common/desirable for built
in packages to use advice instead of hooks and such?

also, merely as a plea from a user, i hope defadvice will stick around
for all that user and non-built-in and abandoned code.

On 3/31/22, Stefan Monnier  wrote:
> The patch below gets rid of the old `defadvice`, replacing it with
> `advice-add`.
> It also includes some FIXMEs about things I found along the way which
> look suspicious (they're not directly related to the patch, tho, nor
> are they affected by it AFAICT).
>
>
> Stefan
>
>
> 2022-03-31  Stefan Monnier  
>
> Replace all uses of the old `defadvice` with the new `advice-add`.
> Along the way, remove some redundant `:group` args
> (redundant because they specify the same group as would be used by
> default anyway) and make a few other simplifications.
> Also don't bother putting `advice-add` within an eval-after-load
> since the advice machinery already takes care of handling it.
>
> * lisp/org.el (org-run-like-in-org-mode): Strength reduce `eval`
> to `cl-progv`.
> (org--check-org-structure-template-alist): Strength reduce `eval`
> to `symbol-value`.
> (org-map-entries, org-eval-in-calendar, org-diary-sexp-entry):
> Make sure we use the new lexically scoped dialect.
> (org--math-always-on): New function, extracted from advice.
> (org-cdlatex-mode): Use it with `advice-add`.
> (org-self-insert-command): Simplify `and`+`listp` into `consp`.
> (org-submit-bug-report):
> Make sure we use the new lexically scoped dialect.
>
> * lisp/org-protocol.el (org-protocol-convert-query-to-plist):
> Use `cl-mapcan`.
> (org--protocol-detect-protocol-server): New function, extracted
> from advice.
> (server-visit-files): Use it with `advice-add`.
>
> * lisp/org-mouse.el (org--mouse-dnd-insert-text): New function,
> extracted
> from advice.
> (dnd-insert-text): Use it with `advice-add`.
> (org--mouse-dnd-open-file): New function, extracted from advice.
> (dnd-open-file): Use it with `advice-add`.
> (org--mouse-open-at-point): New function, extracted from advice.
> (org-mode-hook): Advise `org-open-at-point` with `advice-add`.
>
> * lisp/org-ctags.el (org--ctags-load-tag-list): New function, extracted
> from advice.
> (visit-tags-table): Use it with `advice-add`.
> (org--ctags-set-org-mark-before-finding-tag): New function, extracted
> from advice.
> (xref-find-definitions): Use it with `advice-add`.
>
> * lisp/org-compat.el (org-bookmark-jump-unhide): Accept (unused) args.
> (save-place-find-file-hook): Use `advice-add`.
> (org--ecb-show-context): New function, extracted from advice.
> (ecb-method-clicked): Use it with `advice-add`.
> (org-mark-jump-unhide): Accept (unused) args.
> (pop-to-mark-command, exchange-point-and-mark, pop-global-mark):
> Use `advice-add`.
>
>
> diff --git a/lisp/org-compat.el b/lisp/org-compat.el
> index 38d330de6d..f768a8233b 100644
> --- a/lisp/org-compat.el
> +++ b/lisp/org-compat.el
> @@ -901,7 +901,6 @@ attention to case differences."
>  (defcustom org-imenu-depth 2
>"The maximum level for Imenu access to Org headlines.
>  This also applied for speedbar access."
> -  :group 'org-imenu-and-speedbar
>:type 'integer)
>
>   Imenu
> @@ -1114,7 +1113,7 @@ ELEMENT is the element at point."
>
>   Bookmark
>
> -(defun org-bookmark-jump-unhide ()
> +(defun org-bookmark-jump-unhide ( _)
>"Unhide the current position, to show the bookmark location."
>(and (derived-mode-p 'org-mode)
> (or (org-invisible-p)
> @@ -1123,7 +1122,7 @@ ELEMENT is the element at point."
> (org-show-context 'bookmark-jump)))
>
>  ;; Make `bookmark-jump' shows the jump location if it was hidden.
> -(add-hook 'bookmark-after-jump-hook 'org-bookmark-jump-unhide)
> +(add-hook 'bookmark-after-jump-hook #'org-bookmark-jump-unhide)
>
>   Calendar
>
> @@ -1176,42 +1175,29 @@ key."
>   Saveplace
>
>  ;; Make sure saveplace shows the location if it was hidden
> -(eval-after-load 'saveplace
> -  '(defadvice save-place-find-file-hook (after org-make-visible activate)
> - "Make the position visible."
> - (org-bookmark-jump-unhide)))
> +(advice-add 'save-place-find-file-hook :after #'org-bookmark-jump-unhide)
>
>   Ecb
>
>  ;; Make sure ecb shows the location if it was hidden
> -(eval-after-load 'ecb
> -  '(defadvice ecb-method-clicked (after esf/org-show-context activate)
> - "Make hierarchy visible when jumping into location from ECB tree
> buffer."
> - (when (derived-mode-p 'org-mode)
> -   (org-show-context
> +(advice-add 'ecb-method-clicked :after #'org--ecb-show-context)
> +(defun org--ecb-show-context ( _)
> +  "Make hierarchy visible when jumping into location from ECB tree
> buffer."
> +  (when (derived-mode-p 'org-mode)
> +(org-show-context)))
>
>   Simple
>
> -(defun org-mark-jump-unhide ()
> 

Re: [BUG] Agenda no longer works for timestamps inside properties drawer [9.5.2 (release_9.5.2-24-g668205 @ /home/ignacio/repos/emacs/lisp/org/)]

2022-03-23 Thread Samuel Wales
* x2
> Could you elaborate? Maybe provide an example.

idk if this answers your q or not.

it rambles.

for context some goals include orthogonality, satisfying
strong differing views/needs with little complexity, and
having simple rules or transparency for knowing behavior
e.g. what shows up in an agenda view.

by line comments i mean "# " in recent org since 9 or so and
"#" in org up until then.  with leading spaces or whatever.

for clarity i will treat COMMENT quasi-kw separately if at
all.  it is like ARCHIVE.

fundamentally line comments prevent lines from being
exported.  so you could do

\* my header to be exported via subtree export
# NOTE TO SELF: see https://google.com for more on this.
# fixme see https://whatever.whatever for new change
something that will actually export

and that was just for yourself.  it would not get exported.
for reference.

and the link would be for this case highlighted and
clickable [and show up in agenda text view].

idr the details now, but links were clickable without being
highlighted at one point, and accidental clicks were
dangerous.  you could work around that with font lock and
idk what changes have occurred since then.

i have just described the "line comments mean don't show in
export" rule.  the intuition of some has been that links
should as above still be useful, even though they do not
export.  comenting is mostly related to exporting.

others have thought commenting means commenting.  they think
there should be no semantics at all when you comment links.
thus, links are inert pieces of text.  if you want to go to
google then you copy the text and paste it into a browser.

===

up to here i have described links.  but ts issues are
similar to links.  e.g. fontifying and clicking.

they are supposed to show up in daily/weekly for the date of
the ts.  except when they are not supposed to.  which varies
by preference.  (which is reolated to the currentish
controversyish wrt drawers and blocks --- i am saying line
comments are a valid similar consideration.  i have a
possible solution for all.)

for a non-exporting entry, you might want to comment out a
ts so it does not show up.  what is canonical there?  the
second type of user says just comment it.  the first type of
user says tses should be useful in comments.

\* my header to be exported via subtree export
# i wrote this paragraph on this date: [2022-03-23 Wed]
something that will actually export

or the active ts version.  tses are also highly useful to
see fontified and be clickable analogously to links.  (to
the first type of user.)  you might want to know the changes
you made to your docuyment on that date, so it shows in
daily/weekly agenda [stndard disclaimes like in log mode if
inactive etc.].  you should not be restricted to text search
to find a ts or a range of tses.

you want things to be able to show up nd still not be
exported.

some would say if it is fontified, you know it is a ts; it's
visually useful even if you do not use the semantics.

some might make the point that fundamentally active tses are
meant to show up by default in daily/weekly and if you want
something to not show up in non-log-mode you should just
make it inactive.

you could consider daily/weekly being different from text
search to be an inconsistency which requires fixing by
making it transparent, one possibility being making it in a
variable saying where tses will show up.

===

so to a solution for most of this.  i rambled and idk what
you are asking for.

first, i made a mistake due to brain not working, in my
parenthetical examples, but i think you got the idea.

just to get that part nailed down even though it was
probably obvious, vars can contain sets.  thus, a single var
can dictate e.g. what shows up in daily/weekly agenda.  if a
ts is in a context that is mentioned in a member of var,
then it shows up in daily/weekly agenda view.  the var's
value could be e.g. '(properties-drawers line-comments).
(perhaps modulo some reasonable thing to do for body text,
headers, etc. where it is not worth having them be
explicitly members in that var or so.)

thus if some users want tses in properties drawers (or
source blocks, or line comments) to show up in daily/weekly
and other users do not, then this might be a solution for
satisfying both types of users, and also those who have n>1
use case (sometimes one and soetimes the other).  and
changing default would be trivial and user can change it and
user can c-h v thus the user does not have to guess about
behavior or think about org versions or pull hair out trying
to comment something out from showing up or GET it to show
up.

note that this reduces a bunch of potential variables down
to just one.  merely: what shows up in daily/weekly view.

for some purposes, you cn sticik this variable in a custom
command clause.

for completeness, other considerations exist like
clickability (viz. in what contexts should a ts or link be
clickable?  perhaps all thus no need to 

Re: [BUG] Agenda no longer works for timestamps inside properties drawer [9.5.2 (release_9.5.2-24-g668205 @ /home/ignacio/repos/emacs/lisp/org/)]

2022-03-22 Thread Samuel Wales
On 3/22/22, Ihor Radchenko  wrote:
> lax - agenda may match anything date-looking (with or without brackets).
> A specialized regex agenda matcher with regex constructed using current
> agenda date.
>
> Maybe we can introduce a new agenda view? Or maybe a special agenda
> mode, similar to org-agenda-include-inactive-timestamps?

over the years i have seen different opinions on contexts in which
tses [and links, not to make it more complex but to in principle
strive for some type of orthogonality iff discussion goes there]
should show up in agenda and where it should not.

[as a same page type of check, for tses we are talking about
"daily/weekly" which has different semantics from search agenda and
cannot be reproduced with search agenda via parameterization.]

another context [not to create controversy but also for in principle
orthogonality] is line comments, which some think should mean tses and
links therein should not show up in agenda and not fontify and not be
clickable [rule = "remove tses and links from org semantics and
fontification including agenda but not including certain org searchers
like org-occur-in-agend-files"], while others think should mean
"remove from all export" [use case: so you as author can document
exportable stuff inline using comments and still have your tses show
up in daily/weekly if you want that and have clickable links without
having those exposed to the recipient of the exported document, etc.].
links in line comments can be worked around with a bit of code, but
idk about tses.  some will want tses commentable.  some not.

your idea of expanding to other date-like things is an interesting
idea, and so is making an analogy with log mode.

another possibility is to satisfy the preferences users have expressed
[and those with n>1 needs] using a single variable that contains the
contexts that should show in daily/weekly agenda.  org uses multi-item
variables more frequently in recent years [e.g.
org-show-context-detail or visibility for sparse trees] which reduces
vars.  you might have had log mode items in mind, which is similar.

thus in principle it need not be a mode like log mode items, but could
be in agenda custom commnds.

i think a whole view [unlike log mode and tag filtering] might be
confusing to newcomers as [just as with sorting and log mode items and
allow COMMENT and allow ARCHIVE] the regular daily/weekly view is
parameterizable.

i know i got confused by the todo view, wondering if it was something
not creatable with parameterization.

so i would go for your second idea, or the var.  i do think different
preferences exist out there, some strong.

with one or the other, future defaults are trivially changed,
transparent/discoverble by user, and open to user change.

[one problem now being that users can be not merely surprised, but
unaware that stuff is missing from agenda.]

>
> Best,
> Ihor
>



Re: [BUG] Agenda no longer works for timestamps inside properties drawer [9.5.2 (release_9.5.2-24-g668205 @ /home/ignacio/repos/emacs/lisp/org/)]

2022-03-21 Thread Samuel Wales
this is merely intuition, but i can

- understand why planning line tses should not be matched in various
places; they are closely tied to real org entries
- not quite grasp why bare active and inactive tses should not be
matched by ts agenda almost anywhere including blocks.  perhaps the
idea is that you might wnt to store lots of data with tses and they
would be too much clutter?
- understand that there are probably plenty of implementation issues
that might obtrude and should be respected

so i guess i am interested in the rationale.  example of ts [and text]
search being useful might be an example or ledger block that contains
ledger source, or something like that.  i can get why bare ts not
being matched inside links might be useful.

otoh i can get why text [not ts] and isearch search inside of links
can be useful.

idk if my intuitions match those of others.  i am partly trying to
think of what a newcomer might expect to work [and the simplicity of a
rule that he or she would have to remember in order to know what the
behavior will be].


On 3/21/22, Ignacio Casso  wrote:
>
>>> What you see in the new Org version is not a bug. Property values are
>>> treated as plain text by Org.
>>>
>>> I was unable to find a place in manual describing that timestamps cannot
>>> be placed inside property values:
>
>>> I personally see allowing timestamps (and links) inside property values
>>> as a useful feature.
>>> Would it be of interest for other users?
>>
>> Yes, it's a quite useful feature. For years, via my Capture templates,
>> I've been adding a property named :Created: to the properties drawer as
>> follows:
>>
>> :PROPERTIES:
>> :Created:  <2022-03-06 Sun 22:42>
>> :END:
>>
>> Now, in 9.5.2, literally hundreds of entries that formerly appeared on the
>> built-in Agenda views cannot be easily found.
>
>
> It seems that I'm not the only one using this unintended feature in
> previous versions of org, and probably there will be many others who
> don't use the latest version of org and have not noticed yet but will
> have the same problem when they upgrade.
>
> I think that even if timestamps were never intended to be used inside
> property drawers before, the fact that it worked for a long time and
> nothing in the documentation suggested otherwise makes it a de facto
> feature, even if unintended, and should be preserved.
>
> I've located the line in org-agenda.el responsible of the new behavior,
> and the following patch seems to fix it. I suggest it is incorporated
> into the repository, maybe with a variable
> org-agenda-skip-timestamps-in-properties-drawer defaulting to t if not
> everyone agrees.
>
>


-- 
The Kafka Pandemic

A blog about science, health, human rights, and misopathy:
https://thekafkapandemic.blogspot.com



Re: [BUG] LOGBOOK makes property search (in org-agenda) too slow(?)

2022-03-12 Thread Samuel Wales
are there intereim workarounds like semi-automatically moving large
logbook entries, or entire logbooks, to a task that says "was logbook
for ..." and then archiving that task?  or automatically archiving old
logbook entries?


On 3/12/22, Ihor Radchenko  wrote:
> "fr...@t-online.de"  writes:
>
>> I have just one headline and do a simple property search (prop1="blah1")
>> for the 'org-agenda', but this takes about 10 seconds!
>
> Thanks for providing a reproducible example! We know about this
> performance issue. Performance has been improved in the development
> version of Org (not released yet). Using your example, agenda generation
> is instant on main.
>
> Best,
> Ihor
>
>


-- 
The Kafka Pandemic

A blog about science, health, human rights, and misopathy:
https://thekafkapandemic.blogspot.com



fyi, a package for communication between org and gui browser

2022-03-01 Thread Samuel Wales
in sacha's list:

https://github.com/bitspook/spookfox

have not tried it, but it looks like it might end up being useful for
too many firefox tabs, annotation of web locations, reusing of ff
tabs, bidir capture-ish things.

-- 
The Kafka Pandemic

A blog about science, health, human rights, and misopathy:
https://thekafkapandemic.blogspot.com



Re: Custom TODO states for one item

2022-02-26 Thread Samuel Wales
you can noly have one todo kw per heading that is meaningful to org.
you can use tags.

there are quasi-kw like archive and comment, however.


On 2/26/22, Ken Mankoff  wrote:
> Hello,
>
> I have a file with custom TODO states:
>
> #+TODO: FOO(f@/@) | BAR(b@/@)
>
> I have one item (heading) within that file that I'd like to have different
> TODO states. Is this possible?
>
> Thanks,
>
>   -k.
>
>
>


-- 
The Kafka Pandemic

A blog about science, health, human rights, and misopathy:
https://thekafkapandemic.blogspot.com



Re: profiling latency in large org-mode buffers (under both main & org-fold feature)

2022-02-21 Thread Samuel Wales
i have been dealing with latency also, often in undo-tree.  this might
be a dumb suggestion, but is it related to org file size?  my files
have not really grown /that/ much but maybe you could bisect one.  as
opposed to config.

i am not saying that your org files are too big.  just that maybe it
could lead to insights.


On 2/21/22, Matt Price  wrote:
> I'm trying to figure out what causes high latency while typing in large
> org-mode files.  The issue is very clearly a result of my large config
> file, but I'm not sure how to track it down with any precision.
>
> My main literate config file is ~/.emacs.d/emacs-init.org, currently 15000
> lines, 260 src blocks.
> If I create a ~minimal.el~ config like this:
>
> (let* ((all-paths
>   '("/home/matt/src/org-mode/emacs/site-lisp/org")))
> (dolist (p all-paths)
>   (add-to-list 'load-path p)))
>
>   (require 'org)
>   (find-file "~/.emacs.d/emacs-init.org")
>
> then I do not notice any latency while typing.  If I run the profiler while
> using the minimal config, the profile looks about like this at a high
> level:
>
> 1397  71% - command-execute
>  740  37%  - funcall-interactively
>  718  36%   - org-self-insert-command
>  686  34%+ org-element--cache-after-change
>   10   0%+ org-fold-core--fix-folded-region
>3   0%+ blink-paren-post-self-insert-function
>2   0%+ jit-lock-after-change
>1   0%
> org-fold-check-before-invisible-edit--text-properties
>9   0%   + previous-line
>6   0%   + minibuffer-complete
>3   0%   + org-return
>3   0%   + execute-extended-command
>  657  33%  - byte-code
>  657  33%   - read-extended-command
>   64   3%- completing-read-default
>   14   0% + redisplay_internal (C function)
>1   0% + timer-event-handler
>  371  18% - redisplay_internal (C function)
>  251  12%  + jit-lock-function
>   90   4%  + assq
>7   0%  + substitute-command-keys
>3   0%  + eval
>  125   6% + timer-event-handler
>   69   3% + ...
>
> --
> However, if I instead use my fairly extensive main config, latency is high
> enough that there's a noticeable delay while typing ordinary words. I see
> this  regardless of whether I build from main or from Ihor's org-fold
> feature branch on github. The profiler overview here is pretty different --
> redisplay_internal takes a much higher percentage of the CPU requirement:
>
>  3170  56% - redisplay_internal (C function)
>  693  12%  - substitute-command-keys
>  417   7%   + #
>   59   1%  + assq
>   49   0%  + org-in-subtree-not-table-p
>   36   0%  + tab-bar-make-keymap
>   35   0%and
>   24   0%  + not
>   16   0%org-at-table-p
>   13   0%  + jit-lock-function
>8   0%keymap-canonicalize
>7   0%  + #
>4   0%  + funcall
>4   0%display-graphic-p
>3   0%  + #
>3   0%file-readable-p
>3   0%  + table--probe-cell
>3   0%table--row-column-insertion-point-p
> 1486  26% - command-execute
> 1200  21%  - byte-code
> 1200  21%   - read-extended-command
> 1200  21%- completing-read-default
> 1200  21% - apply
> 1200  21%  - vertico--advice
>  475   8%   + #
>
> --
> I've almost never used the profiler and am not quite sure how I should
> proceed to debug this.  I realize I can comment out parts of the config one
> at a time, but that is not so easy for me to do in my current setup, and I
> suppose there are likely to be multiple contributing causes, which I may
> not really notice except in the aggregate.
>
> If anyone has suggestions, I would love to hear them!
>
> Thanks,
>
> Matt
>


-- 
The Kafka Pandemic

A blog about science, health, human rights, and misopathy:
https://thekafkapandemic.blogspot.com



Re: Suggestion: convert dispatchers to use transient

2022-02-05 Thread Samuel Wales
jus want to state the obvious here in case it is useful [but everybody
probbly lready knows] --- not everybody uses packages or maybe trusts
them has internet etc.

On 2/5/22, João Pedro de Amorim Paula  wrote:
> On 04 February 2022 08:30, Tim Cross  wrote:
>
>> I'm assuming it is, but I have to admit I'm still not 100% clear on
>> how Emacs handles the situation where you use a library that is both
>> built-in and available in ELPA. Does Emacs use the latest version
>> available or does it use the built-in version until you explicitly
>> select the ELPA versions?
>
> Welp, I happened to ponder the same question after trying to implement a
> function to install packages that are not installed already (I'm not
> using any helper configuration such as use-package, which would already
> handle this). From what I gathered empirically, it appears that if
> something is built-in, Emacs' package.el won't try to install -- it
> checks with package-installed-p on any call to package-install, which
> checks if the package is built-in with package-built-in-p as a fallback
> on cond --, but you can force installation from the archives by passing
> a package description object (defined as package-desc on package.el)
> instead of a symbol
>
> (let ((pkg-desc (assq 'org package-archive-contents)))
>   (package-install pkg-desc))
>
> and Emacs seems to be loading the newest version when it is a dependency
> of something else. Though I'm not really sure, as most of the packages I
> have from ELPA have the same version as the ones built-in on Emacs
> 28.0.91. I'll try and install Emacs 27 to check this out.
>
> In the mean time, I guess this would be a good opportunity to share a
> couple of functions I have with the purpose of installing packages.
>
> (defun pkg-description (package)
>   "Return the description for PACKAGE.
> If PACKAGE is installed, the will be present on `package-alist',
> otherwise look for it in `package-archive-contents'."
>   (or (cadr (assoc package package-alist))
>   (cadr (assoc package package-archive-contents
>
> (defun pkg-ensure-archive (package)
>   "Install PACKAGE from the archives, if not already installed."
>   (when-let ((pkg-desc (pkg-description package)))
> (unless (package-installed-p pkg-desc)
>   (package-install-from-archive pkg-desc
>
> (defun require-package (package  force)
>   "Ensure that PACKAGE is installed.
> If FORCE is non-nil, force installation regardless if PACKAGE is
> built-in or not.
>
> First, use `package-installed-p' to check if PACKAGE was
> installed via the Emacs package manager, otherwise, try to
> `require' PACKAGE; this ensures that we don't require PACKAGE if
> it was installed using the package manager. If both of those
> fail, run `package-refresh-contents' and install PACKAGE."
>   (unless (and (not force)
>(or (package-installed-p package)
>(require package nil 'no-error)))
> (unless (assoc package package-archive-contents)
>   (package-refresh-contents))
> (if force
> (pkg-ensure-archive package)
>   (package-install package
>
> On the last one, the main function that I use, if FORCE is non-nil it
> will download and install the package from the archives even if it is
> built-in.
>
> Best regards,
>
> --
> João Pedro de Amorim Paula
> IT undergraduate at Universidade Federal do Rio Grande do Norte (UFRN)
>


-- 
The Kafka Pandemic

A blog about science, health, human rights, and misopathy:
https://thekafkapandemic.blogspot.com



Re: Yet another browser extension for capturing notes - LinkRemark

2022-01-19 Thread Samuel Wales
just a quick fwiw before i try to reply to the longer message by max.
my own suggestion is modest for metadata, [even for science papers and
things with funny web construction].  just title like org-capture
extension.  no need to cite in my case.

my needs for saving and restoring, however, are more fancy.  something
like achieving a 1:1 mapping from firefox selected tabs, or a tree
style tabs extension tree, to their counterparts in org, even when
those counterparts have notes and such.  this might include marking
the org version as deleted/doneified] merely by closing tab in
firefox.  vice-versa would be straightforward.  so it's really a "get
organized and don't get confused by having both firefox and org" kinda
thing.



Re: Yet another browser extension for capturing notes - LinkRemark

2022-01-17 Thread Samuel Wales
my amazon example was silly and confusing.  the point isn't shopping
for something; it's anything.  science papers, news outlets, nerd
blogs.

On 1/16/22, Samuel Wales  wrote:
> more below.
>
> On 12/26/20, Maxim Nikulin  wrote:
>> On 26/12/2020, Samuel Wales wrote:
>>
>>> [... i can imagine great things possible with such extensions. for
>>> example, you could have sets of tabs, selected by right click in
>>> firefox, to save to a bunch of org entries.  then you could load that
>>> particular set of entries into firefox whenever you want.  and you
>>> could keep notes on each page and move the entries wherever you want.
>>> this would be useful for such things as "i am researching rice
>>> cookers; these are my tabs, but i don't want them cluttering firefox
>>> and i want them with my org notes and to make notes on them and will
>>> re-load them into firefox when i want to revisit".]
>>
>> It should be possible since some tab management extension were used in
>> mozilla to evaluate if webextensions are mature enough and if support of
>> XUL add-ons could be dropped. On the other hand do not expect such
>> feature soon. A kind of semi-blocker is absence of automatic tests to
>> run before every release, and it will require a lot of time.
>
> interesting.  i do note tab selection features in recent firefox-esr
> and i was just assuming something like that.
>
>>
>> In the meanwhile, have you looked at the following comment?
>> https://github.com/sprig/org-capture-extension/issues/12#issuecomment-323569334
>> alphapapa commented Aug 20, 2017
>>
>>> You can do this with the "Copy all URLs" extension (ID:
>>> djdmadneanknadilpjiknlnanaolmbfk). Use this as the custom format (note
>>> the linebreak):
>>>
>>> [[$url][$title]]
>>
>> I am almost sure that similar extension should exist for Firefox as well.
>
> i think this is for copying all tabs, not selected ones.  so a
> workaround for my idea would be to have a fresh firefox window
> dedicated to rice cookers and then save them all.  bit it does not
> save over existing canonical location for each url or similar.
>
> which would be needed for my idea so as to not have duplicates etc.
>
> also i think this extension does not exist any more in firefox.  i
> used to use it for storing as org links.  but it was just to store
> links in case firefox screwed up session restore.  which it usually
> does.  for that purpose, i use one that does not save as orglinks.
>
>>
>> Some points should be clarified in my opinion
>>
>> - Do you expect that metadata should be captured in addition to URLs and
>> titles? Browsers can unload some tabs making page content unavailable.
>
> i wouldn't need this i think.  i'd want page title, just as in
> ordinary org links, but in principle that can be assumed from the
> existing org entry if exists, and if not exists and you are capturing,
> the page is already loaded.  so i think not a metadata issue.
>
>> - Are you going to capture reviews of "rice cookers" that could be
>> considered as ordinary pages or you are going to save items from online
>> stores? I do not current state of affairs but I have heard about some
>> activity for special metadata that allows search engines to display
>> products in a special way. Could you inspect head element of pages in
>> your favorite stores contains desired metadata using page source or
>> inspect element tools?
>
> my web knowledge is too limited to understand your question, but i am
> just hoping it would capture ordinary amazon links, review sites, and
> so on.  and i never use js if i can avoid it so i'm expecting pretty
> normal website stuff i think.  so i'm flexible.
>
> [of course, amazon per se links might need cleaning or uniquification
> of some type for finding the version in org maybe, or maybe for
> improving privacy by removing amazon's data about you in the url, but
> that might not even need any special amazon link knowledge.
> [fanciness might look for the amazon id, if implementer willing or
> somethign exists for that.]]
>
>> - Should tab group be captured as single Org heading or it should be a
>> tree with a section per tab? I am not sure that capture will have no
>> problem with subtree. Certainly Emacs interface for org-protocol +
>> capture are not suitable for sending each tab as a separate link.
>> Another option is to create nested lists, anyway org formatter in my
>> extension need improvements. Are you expecting headings subtree or
>> nested lists?
>
> the status quo is that there is nothin

Re: Yet another browser extension for capturing notes - LinkRemark

2022-01-16 Thread Samuel Wales
more below.

On 12/26/20, Maxim Nikulin  wrote:
> On 26/12/2020, Samuel Wales wrote:
>
>> [... i can imagine great things possible with such extensions. for
>> example, you could have sets of tabs, selected by right click in
>> firefox, to save to a bunch of org entries.  then you could load that
>> particular set of entries into firefox whenever you want.  and you
>> could keep notes on each page and move the entries wherever you want.
>> this would be useful for such things as "i am researching rice
>> cookers; these are my tabs, but i don't want them cluttering firefox
>> and i want them with my org notes and to make notes on them and will
>> re-load them into firefox when i want to revisit".]
>
> It should be possible since some tab management extension were used in
> mozilla to evaluate if webextensions are mature enough and if support of
> XUL add-ons could be dropped. On the other hand do not expect such
> feature soon. A kind of semi-blocker is absence of automatic tests to
> run before every release, and it will require a lot of time.

interesting.  i do note tab selection features in recent firefox-esr
and i was just assuming something like that.

>
> In the meanwhile, have you looked at the following comment?
> https://github.com/sprig/org-capture-extension/issues/12#issuecomment-323569334
> alphapapa commented Aug 20, 2017
>
>> You can do this with the "Copy all URLs" extension (ID:
>> djdmadneanknadilpjiknlnanaolmbfk). Use this as the custom format (note
>> the linebreak):
>>
>> [[$url][$title]]
>
> I am almost sure that similar extension should exist for Firefox as well.

i think this is for copying all tabs, not selected ones.  so a
workaround for my idea would be to have a fresh firefox window
dedicated to rice cookers and then save them all.  bit it does not
save over existing canonical location for each url or similar.

which would be needed for my idea so as to not have duplicates etc.

also i think this extension does not exist any more in firefox.  i
used to use it for storing as org links.  but it was just to store
links in case firefox screwed up session restore.  which it usually
does.  for that purpose, i use one that does not save as orglinks.

>
> Some points should be clarified in my opinion
>
> - Do you expect that metadata should be captured in addition to URLs and
> titles? Browsers can unload some tabs making page content unavailable.

i wouldn't need this i think.  i'd want page title, just as in
ordinary org links, but in principle that can be assumed from the
existing org entry if exists, and if not exists and you are capturing,
the page is already loaded.  so i think not a metadata issue.

> - Are you going to capture reviews of "rice cookers" that could be
> considered as ordinary pages or you are going to save items from online
> stores? I do not current state of affairs but I have heard about some
> activity for special metadata that allows search engines to display
> products in a special way. Could you inspect head element of pages in
> your favorite stores contains desired metadata using page source or
> inspect element tools?

my web knowledge is too limited to understand your question, but i am
just hoping it would capture ordinary amazon links, review sites, and
so on.  and i never use js if i can avoid it so i'm expecting pretty
normal website stuff i think.  so i'm flexible.

[of course, amazon per se links might need cleaning or uniquification
of some type for finding the version in org maybe, or maybe for
improving privacy by removing amazon's data about you in the url, but
that might not even need any special amazon link knowledge.
[fanciness might look for the amazon id, if implementer willing or
somethign exists for that.]]

> - Should tab group be captured as single Org heading or it should be a
> tree with a section per tab? I am not sure that capture will have no
> problem with subtree. Certainly Emacs interface for org-protocol +
> capture are not suitable for sending each tab as a separate link.
> Another option is to create nested lists, anyway org formatter in my
> extension need improvements. Are you expecting headings subtree or
> nested lists?

the status quo is that there is nothing, so using lists would be a
huge improvement and work great.  but fanciness by using org sections
if poss [i assume this means header and metadata and content and maybe
descendents] could be more flexible.

>
>> [now if i can only debug the extra-blank-lines-in-capture problem.]
>
> Fully agree that it is really annoying. It is among high priority items
> in my TODO list.

we might be talking about different thinks.  i am referring to
something in org that adds blank lines when my particular org capture
templates are used.

Re: Converting document from hard whitespace indentation to org-indent-mode

2022-01-12 Thread Samuel Wales
i think that default has changed to your preference in recent versions
[according to ml discussions].  which, i agree with.

On 1/12/22, Max Brieiev  wrote:
>
> Several of my documents use indentation to line up with the headings,
> like below:
>
> * Top level headline
>   paragraph
>   + list item lorem ipsum
> dolor sit amet
> ** Second level
>some text
> *** Third level
> more text
>
> I would like to strip leading whitespace, so that I could switch to
> =org-indent-mode= to have a nice view of the document instead of using
> hard whitespace indentation.
>
> Basically I want to:
> - strip leading whitespace,
> - but preserve the indentation of lists and src blocks
> - refill all paragraphs according to what =org-fill-paragragh= would do.
>
> How would I do it programmatically? My current Elisp knowledge is poor.
>
> Thanks in advance.
>
>


-- 
The Kafka Pandemic

A blog about science, health, human rights, and misopathy:
https://thekafkapandemic.blogspot.com



Re: Question Regarding Creating Workflow For Automatic Formulas For Finance Based Org Spreadsheet

2022-01-10 Thread Samuel Wales
fwiw, my experience: double entry is what i found ledger useful for.
iiuc it is that transactions go from one place to another, which felt
intuitive to me.

anything else, such as taking monthly averages, didn't end up as i
expected.  weird concept of average to me, and v3 bugs with floating
point etc.  i could never get them to be pretty.

so the example you give of ledger's rough edge is actually the one
non-rough-edge i found in ledger.  in org, i hae a shell babel block
ad an exampale or ledge block for data.

i find it strange that agenda searching doesn't find stuff in the
ledger data block, and would want org dates if poss.  i did not try to
use ledger properly with its emacs mode.


On 1/10/22, Marcin Borkowski  wrote:
>
> On 2022-01-10, at 18:01, Samuel Banya  wrote:
>
>> The 'double reporting' idea might have been why I just flat out shook my
>> head when I saw the one presentation on 'ledger' in Emacs on YouTube a
>> while ago as its a bit too complicated and unnecessary for a layman.
>>
>> I just don't need that kind of over-thinking when it comes to my finances
>> since I just need a spreadsheet that listed expenses, and to count totals.
>> That's about it.
>
> You may think it's overthinking... unless you encounter one of the many
> /real-world problems/ the double-accounting system was /designed/ to
> solve.
>
> A classic example is when you buy something on day X (expense) but pay
> for it on day Y (cash outflow), and you want to be able to record both
> dates.
>
> Or you have some irregular costs (like paying for a car insurance once
> a year) and you want to spread them more evenly over a longer period, so
> that your /cash outflow/ is recorded once a year, but the associated
> /cost/ is recorded every month.  (This may help tremendously with
> budgeting.)
>
> Or you decide to transfer money between two bank accounts (both yours),
> but money going from account A arrives at account B after one day (or
> even later).
>
> Or you buy something for someone and he pays you back a few days (or
> weeks, or months) later, or not at all (which may happen).
>
>
> As you might notice, the first two examples are situations when the
> /expense/ and /cash outflow/ are detached in time - something
> /extremely/ common in business, but also pretty common in personal
> finance.  You might say that you don't care - and I understand that -
> but it is actually very useful to track /both/ expenses (so that you
> know your cost of living etc.) and cash in- and outflows (so that you
> can reconcile your ledger with your cash/bank account etc., to ensure
> you didn't make any mistake).  (If you - like most people, I assume -
> barely have liquidity, tracking cash flows may become even more
> important.)  Also, the difference in time between income/expenses and
> cash flow may become /extremely/ important when calculating taxes.
>
> The third example is also connected with things happening at different
> moments in time, though to be fair, if you're only interested in actual
> /expenses/, you probably wouldn't even want to record that.
>
> The last example is similar to the third one - it's not an /expense/ per
> se, but again - tracking cash is useful, tracking your assets and
> liabilities (in that case, money you owe to other people and money other
> people owe to you) is /extremely/ useful, even just as an individual,
> and if that guy /doesn't/ pay you back (mind you, this may happen for
> /legitimate/ issues, like death), it can actually /become/ an expense.
>
> Also, using accounting software makes things like calculating your net
> worth trivial.  And there are other issues which can quickly become
> pretty hairy when you try to wrap you head around them with a simple
> spreadsheet (like dealing with various currencies/stock/commodities with
> varying prices, for instance), but which have standard, well-known
> solutions in the world of accounting.
>
>
> Actually, I'd argue that learning the basics of accounting could help
> a /layman/ better manage their finances.  While the technicalities of
> bookkeeping are not relevant to that, the general ideas like cash flow,
> income and expenses, balance sheet, assets and liabilities, liquidity,
> compound interest etc. provide a very useful way of thinking about
> money.  Two examples.  A friend of mine (an economist) was asked to
> conduct a 45-minute class for high-schoolers about economics (and
> finance, I guess).  He decided that if these kids are to have any use of
> that class, he should gice them a few sentences - "anchors", I'd call
> them - which could be some kind of guidelines to use when navigating the
> world of economy (on a scale of a country as well as of a household) and
> finance.  One of these sentences was: "If I don't have enough cash to
> buy , it means I cannot afford it."  It's as simple as that - but
> it goes very much against the message you get from (among others) the
> banking system.  (And yes, there are "exceptions".  But you 

Re: [BUG] org-element-cache bug: org-persist-read persists seemingly forever

2021-12-24 Thread Samuel Wales
20051 135025 938122 other--a.org

this is a smallish to middling file for me.  my largest is 4x larger.
i haven't gotten new org to work yet so i haven't revisited this yet.

On 12/24/21, Ihor Radchenko  wrote:
> Samuel Wales  writes:
>
>> this reproduces most or all of the time.  idk if it is ueful to
>> anybody, but i thought i would post it in case it is instantly
>> recognizable.
>>
>> emacs 25.  latest 9.5 org main.
>>
>> Debugger entered--Lisp error: (quit)
>>   read(#)
>>   org-persist-read(org-element--cache #)
>
> Thanks for reporting!
> Apparently read is being very slow when reading cache for other--a.org
> May I know what is the size of other--a.org?
>
> Next time you see the slowness, could you look into
> `org-persist-directory'/index file, find the other--a.org and look at
> the value of :persist-file property in the same list? Then, can you
> check that persist file size?
>
> Best,
> Ihor
>


-- 
The Kafka Pandemic

A blog about science, health, human rights, and misopathy:
https://thekafkapandemic.blogspot.com



[BUG] org-element-cache bug: org-persist-read persists seemingly forever

2021-12-23 Thread Samuel Wales
this reproduces most or all of the time.  idk if it is ueful to
anybody, but i thought i would post it in case it is instantly
recognizable.

emacs 25.  latest 9.5 org main.

Debugger entered--Lisp error: (quit)
  read(#)
  org-persist-read(org-element--cache #)
  org-mode()
  set-auto-mode-0(org-mode nil)
  set-auto-mode()
  normal-mode(t)
  after-find-file(nil t)
  find-file-noselect-1(# "org/other--a.org" nil
nil "org/other--a.org" (27263474 65025))
  find-file-noselect("org/other--a.org" nil nil nil)
  find-file("org/other--a.org")
  alpha-org-find-agenda-files()
  run-hooks(after-init-hook delayed-warnings-hook)
  command-line()
  normal-top-level()


On 12/23/21, Samuel Wales  wrote:
> more below.
>
> On 12/20/21, Ihor Radchenko  wrote:
>> Thanks for reporting!
>>
>> I just pushed the fix upstream.
>
> thank you.
>
> fyi, i am still trying to get main to work.  there is bug in most
> recent main where org element use cache being set to t makes loading
> infinite.  and another where c-x c-c is very slow but there aren't
> messages saying what it is doing.
>
> the cache bug reproduced a few times reliably and i finally figured
> out getting it to debug on quit to give you a bt but then it didn't
> reproduce, so idk if it is intermittent or my brain is not working.
> also, if i quit at the wrong time, cache tells me to hit quit more
> times because it captures that signal.  as i am limited in computer
> use upgrading org is going to take some time.  however, the only
> reason i want to try main is to run the fast batch archiving.  maybe
> bugfix would work for ordinary use.  have not tried it yet.
>
>> supporting latest Emacs - 2 versions [1]. Emacs 28 is going to be
>> released in a few months, bundling Org 9.5. If you can, please update
>> your Emacs to at least version 26.
>
> [thanks.  i dread this.  i have been dreading having to upgrade debian
> and idk when i will be able to but have to do it.  and getting a
> signed emacs and installing it might be more trouble than it seems at
> first as every sw [even org] seems to be.]  still trying.
>


-- 
The Kafka Pandemic

A blog about science, health, human rights, and misopathy:
https://thekafkapandemic.blogspot.com



Re: next-error for agenda searches

2021-12-23 Thread Samuel Wales
===
Hmm... I myself went through several refactors of my Org file
structures. Exactly because things become unmaintainable over time. It
is hard to design a good structure without enough experience with the
old one.
===

[my forest structure is actually pretty good.  it is partly that i
ahve more stuff than i need from years of adding stuff.  regular tasks
to organize and delete stuff is not within my capabilities at this
time.  so i am trying to delete stuff as i go.  if i get annoyed
enough by a search that i can't find anything, then i can in principle
go through results sometimes and doneify while trying to find what i
want.]

one issue with this great thing called capture is that there is
nothing quite so convenient that does the exact opposite.

[you can regularly purge, if your life/forest is simple enough or you
have the physical ability to do things.  but you can't just
org-doneify-lower-value-stuff-i-captured-when-wasn't-sure-of-their-value-at-the-time
without adding energy, concentration, time, etc.]


On 12/20/21, Samuel Wales  wrote:
> well, i implied it at least.
>
> On 12/20/21, Samuel Wales  wrote:
>> more below.
>>
>> On 12/20/21, Ihor Radchenko  wrote:
>>> If more people are interested, I do not see why next-error integration
>>> cannot be included into Org.
>>
>> nitpick: it already is integrated for sparse tree matches in the
>> outline.  i suggested that if next-error worked for more things, like
>> agenda text and tag matches, then it would be consistent with the
>> existing org next-error functionality.  user would know to try it.
>>
>> --
>> The Kafka Pandemic
>>
>> A blog about science, health, human rights, and misopathy:
>> https://thekafkapandemic.blogspot.com
>>
>
>
> --
> The Kafka Pandemic
>
> A blog about science, health, human rights, and misopathy:
> https://thekafkapandemic.blogspot.com
>


-- 
The Kafka Pandemic

A blog about science, health, human rights, and misopathy:
https://thekafkapandemic.blogspot.com



Re: [bug] File mode specification error: (void-function file-attribute-inode-number)

2021-12-23 Thread Samuel Wales
more below.

On 12/20/21, Ihor Radchenko  wrote:
> Thanks for reporting!
>
> I just pushed the fix upstream.

thank you.

fyi, i am still trying to get main to work.  there is bug in most
recent main where org element use cache being set to t makes loading
infinite.  and another where c-x c-c is very slow but there aren't
messages saying what it is doing.

the cache bug reproduced a few times reliably and i finally figured
out getting it to debug on quit to give you a bt but then it didn't
reproduce, so idk if it is intermittent or my brain is not working.
also, if i quit at the wrong time, cache tells me to hit quit more
times because it captures that signal.  as i am limited in computer
use upgrading org is going to take some time.  however, the only
reason i want to try main is to run the fast batch archiving.  maybe
bugfix would work for ordinary use.  have not tried it yet.

> supporting latest Emacs - 2 versions [1]. Emacs 28 is going to be
> released in a few months, bundling Org 9.5. If you can, please update
> your Emacs to at least version 26.

[thanks.  i dread this.  i have been dreading having to upgrade debian
and idk when i will be able to but have to do it.  and getting a
signed emacs and installing it might be more trouble than it seems at
first as every sw [even org] seems to be.]  still trying.



Re: next-error for agenda searches

2021-12-20 Thread Samuel Wales
well, i implied it at least.

On 12/20/21, Samuel Wales  wrote:
> more below.
>
> On 12/20/21, Ihor Radchenko  wrote:
>> If more people are interested, I do not see why next-error integration
>> cannot be included into Org.
>
> nitpick: it already is integrated for sparse tree matches in the
> outline.  i suggested that if next-error worked for more things, like
> agenda text and tag matches, then it would be consistent with the
> existing org next-error functionality.  user would know to try it.
>
> --
> The Kafka Pandemic
>
> A blog about science, health, human rights, and misopathy:
> https://thekafkapandemic.blogspot.com
>


-- 
The Kafka Pandemic

A blog about science, health, human rights, and misopathy:
https://thekafkapandemic.blogspot.com



Re: next-error for agenda searches

2021-12-20 Thread Samuel Wales
more below.

On 12/20/21, Ihor Radchenko  wrote:
> If more people are interested, I do not see why next-error integration
> cannot be included into Org.

nitpick: it already is integrated for sparse tree matches in the
outline.  i suggested that if next-error worked for more things, like
agenda text and tag matches, then it would be consistent with the
existing org next-error functionality.  user would know to try it.

-- 
The Kafka Pandemic

A blog about science, health, human rights, and misopathy:
https://thekafkapandemic.blogspot.com



[bug] File mode specification error: (void-function file-attribute-inode-number)

2021-12-19 Thread Samuel Wales
emacs 25.1 does not have this function.  this error occurs upon
find-file on an org file in org 9.5.

File mode specification error: (void-function file-attribute-inode-number)

-- 
The Kafka Pandemic

A blog about science, health, human rights, and misopathy:
https://thekafkapandemic.blogspot.com



Re: next-error for agenda searches

2021-12-19 Thread Samuel Wales
manual> These
commands can also be used in ‘*grep*’ buffers, where the hyperlinks are
search matches rather than error messages (*note Grep Searching::).
--- (info "(emacs) Compilation Mode")

it is likely common to have grep and compilation mode open at the same
time.  i think this is like your multiple agenda objection.  no?

On 12/19/21, Samuel Wales  wrote:
> [as an example, i should not have brought up the follow mode example
> at all.  it seems to have only confused readers.  i was trying to
> forestall any suggestions that follow-mode exists and can do the job
> that next-error can is all.  it can't do the same job.]
>
> On 12/19/21, Samuel Wales  wrote:
>> On 12/19/21, Ihor Radchenko  wrote:
>>> multiple agenda views is not an uncommon workflow. You may have daily
>>
>> i think this is a strong objection.  multiple simultaneous agenda
>> views seems to sink my suggestion.
>>
>> can one have multiple simultaneous c-c / buffers?  and multiple
>> grep/occur/compilation shell minor mode?
>>
>> or a grep buffer and an occur buffer and a compilation shell minor
>> mode buffer simultaneously?  what disambiguates those?
>>
>> idk what is done in such cases.  perhaps there is an assumption of a
>> single set of errors at a time, or some buffer local thing.
>>
>>> etc. It would be unclear which agenda view to use when you call
>>> next-error. Last generated? Last visited? What about agenda filters?
>>> Dimmed tasks?
>>
>> yes, good points, if you mean separate agendas.  [else filters
>> honored; dimmed presumably not skipped by default.]
>>
>>>
>>>> furthermore, the next-closest thing, follow mode, puts point in wrong
>>>> window.  also, 'canonical visibility is not present so i cannot see
>>>> everything [this might or might not be fixable by user].
>>>
>>> Can you elaborate?
>>
>> well it is moot because of the accessibility issue, but it is
>> unsuitable for the next-error task.  point in wrong window so you have
>> to switch.  some things hidden so you have to make visible is all i
>> meant.  again, moot so no suggestions needed here.
>>
>>>> also there is an accessibility issue with it.  i use large fonts so 2
>>>> windows do not show much.  i use 2 windows only for very rare
>>>> completion or selecting purposes.  not usable here.
>>>
>>> I also use relatively large fonts, though I do have space for two
>>> windows (but not more). Note that there is org-agenda-entry-text-mode.
>>
>> indeed that shows text.  not editable directly in the real buffer, so
>> not like next-error.  not useful for me in practice but nice.
>>
>> the next-error idea is for consistency with other parts of emacs.
>> your multiple simultaneous agenda problem might nix it, dunno.
>>
>>> Might be useful. Also, I personally prefer org-quickpeek in agenda.
>>
>> can't seem to find that package but next-error allows editing not just
>> peeking.
>>
>>> This sounds like you could use more tight search criteria or custom
>>> agenda searches. An example of irrelevant vs. relevant information could
>>> help us to suggest something for you.
>>
>> appreciate the offfer but pretty ure nobody can help here.  i am also
>> limited in computer use and the back and forth is an issue.  i would
>> not be able to describe the poroblems in sufficient detail, there
>> would be further questions, i'd have to respond, etc.
>>
>> but basically i have had org for a long time and i am not able to
>> maintain my forest as well as i need to.
>>
>> but it was just one point of many.  help here would in most cases
>> likely be smething i have already thought of.  appreciates the offer.
>>
>> next-error is a sort of general tool.  it is not just for this purpose
>> and compilation errors.  imo at least.  that is why c-c / uses it.
>>
>>>
>>>> next-error would help me traverse and trim it rapidly.  i could
>>>> perhaps create a kb macro to emulate it, but i haven't tried yet.
>>>> then again, one could do so for grep mode etc. also.  :]
>>>
>>> If you decide to go with macro, it should not be too hard. Just  on
>>> agenda item, do your edits, macro-beg, switch to agenda buffer,
>>> next-line, , macro-end
>>
>> yes :) [and doing soething to create canonical visibility at point so
>> that everything relevant is visible, and setting line in window].
>>
>> [and finding that kb macro to lisp package and binding the command and
&

Re: next-error for agenda searches

2021-12-19 Thread Samuel Wales
[as an example, i should not have brought up the follow mode example
at all.  it seems to have only confused readers.  i was trying to
forestall any suggestions that follow-mode exists and can do the job
that next-error can is all.  it can't do the same job.]

On 12/19/21, Samuel Wales  wrote:
> On 12/19/21, Ihor Radchenko  wrote:
>> multiple agenda views is not an uncommon workflow. You may have daily
>
> i think this is a strong objection.  multiple simultaneous agenda
> views seems to sink my suggestion.
>
> can one have multiple simultaneous c-c / buffers?  and multiple
> grep/occur/compilation shell minor mode?
>
> or a grep buffer and an occur buffer and a compilation shell minor
> mode buffer simultaneously?  what disambiguates those?
>
> idk what is done in such cases.  perhaps there is an assumption of a
> single set of errors at a time, or some buffer local thing.
>
>> etc. It would be unclear which agenda view to use when you call
>> next-error. Last generated? Last visited? What about agenda filters?
>> Dimmed tasks?
>
> yes, good points, if you mean separate agendas.  [else filters
> honored; dimmed presumably not skipped by default.]
>
>>
>>> furthermore, the next-closest thing, follow mode, puts point in wrong
>>> window.  also, 'canonical visibility is not present so i cannot see
>>> everything [this might or might not be fixable by user].
>>
>> Can you elaborate?
>
> well it is moot because of the accessibility issue, but it is
> unsuitable for the next-error task.  point in wrong window so you have
> to switch.  some things hidden so you have to make visible is all i
> meant.  again, moot so no suggestions needed here.
>
>>> also there is an accessibility issue with it.  i use large fonts so 2
>>> windows do not show much.  i use 2 windows only for very rare
>>> completion or selecting purposes.  not usable here.
>>
>> I also use relatively large fonts, though I do have space for two
>> windows (but not more). Note that there is org-agenda-entry-text-mode.
>
> indeed that shows text.  not editable directly in the real buffer, so
> not like next-error.  not useful for me in practice but nice.
>
> the next-error idea is for consistency with other parts of emacs.
> your multiple simultaneous agenda problem might nix it, dunno.
>
>> Might be useful. Also, I personally prefer org-quickpeek in agenda.
>
> can't seem to find that package but next-error allows editing not just
> peeking.
>
>> This sounds like you could use more tight search criteria or custom
>> agenda searches. An example of irrelevant vs. relevant information could
>> help us to suggest something for you.
>
> appreciate the offfer but pretty ure nobody can help here.  i am also
> limited in computer use and the back and forth is an issue.  i would
> not be able to describe the poroblems in sufficient detail, there
> would be further questions, i'd have to respond, etc.
>
> but basically i have had org for a long time and i am not able to
> maintain my forest as well as i need to.
>
> but it was just one point of many.  help here would in most cases
> likely be smething i have already thought of.  appreciates the offer.
>
> next-error is a sort of general tool.  it is not just for this purpose
> and compilation errors.  imo at least.  that is why c-c / uses it.
>
>>
>>> next-error would help me traverse and trim it rapidly.  i could
>>> perhaps create a kb macro to emulate it, but i haven't tried yet.
>>> then again, one could do so for grep mode etc. also.  :]
>>
>> If you decide to go with macro, it should not be too hard. Just  on
>> agenda item, do your edits, macro-beg, switch to agenda buffer,
>> next-line, , macro-end
>
> yes :) [and doing soething to create canonical visibility at point so
> that everything relevant is visible, and setting line in window].
>
> [and finding that kb macro to lisp package and binding the command and
> possibly overloading the next-error bindings.]
>
>>
>> Best,
>> Ihor
>>
>>
>
> my suggestion was for org's sake and i didn't think this much detail
> would be needed at the time.  i used my computer use time to do the
> best i could, but it seems that more detail was needed, and that
> detail needed discussion.  my bad.
>
> n.b.  i've been on the list for years, and many core features of org,
> and parts thereof, were actually... my suggestions :).
>
> but sometimes i miss the mark apparently, especially lately.  as in this
> case.
>
> still, not sure why multiple grep buffers or grep with occur or c-c /,
> etc. are compatible but multiple simultaneous agenda not so.
>
> --
> The Kafka Pandemic
>
> A blog about science, health, human rights, and misopathy:
> https://thekafkapandemic.blogspot.com
>


-- 
The Kafka Pandemic

A blog about science, health, human rights, and misopathy:
https://thekafkapandemic.blogspot.com



Re: next-error for agenda searches

2021-12-19 Thread Samuel Wales
On 12/19/21, Ihor Radchenko  wrote:
> multiple agenda views is not an uncommon workflow. You may have daily

i think this is a strong objection.  multiple simultaneous agenda
views seems to sink my suggestion.

can one have multiple simultaneous c-c / buffers?  and multiple
grep/occur/compilation shell minor mode?

or a grep buffer and an occur buffer and a compilation shell minor
mode buffer simultaneously?  what disambiguates those?

idk what is done in such cases.  perhaps there is an assumption of a
single set of errors at a time, or some buffer local thing.

> etc. It would be unclear which agenda view to use when you call
> next-error. Last generated? Last visited? What about agenda filters?
> Dimmed tasks?

yes, good points, if you mean separate agendas.  [else filters
honored; dimmed presumably not skipped by default.]

>
>> furthermore, the next-closest thing, follow mode, puts point in wrong
>> window.  also, 'canonical visibility is not present so i cannot see
>> everything [this might or might not be fixable by user].
>
> Can you elaborate?

well it is moot because of the accessibility issue, but it is
unsuitable for the next-error task.  point in wrong window so you have
to switch.  some things hidden so you have to make visible is all i
meant.  again, moot so no suggestions needed here.

>> also there is an accessibility issue with it.  i use large fonts so 2
>> windows do not show much.  i use 2 windows only for very rare
>> completion or selecting purposes.  not usable here.
>
> I also use relatively large fonts, though I do have space for two
> windows (but not more). Note that there is org-agenda-entry-text-mode.

indeed that shows text.  not editable directly in the real buffer, so
not like next-error.  not useful for me in practice but nice.

the next-error idea is for consistency with other parts of emacs.
your multiple simultaneous agenda problem might nix it, dunno.

> Might be useful. Also, I personally prefer org-quickpeek in agenda.

can't seem to find that package but next-error allows editing not just peeking.

> This sounds like you could use more tight search criteria or custom
> agenda searches. An example of irrelevant vs. relevant information could
> help us to suggest something for you.

appreciate the offfer but pretty ure nobody can help here.  i am also
limited in computer use and the back and forth is an issue.  i would
not be able to describe the poroblems in sufficient detail, there
would be further questions, i'd have to respond, etc.

but basically i have had org for a long time and i am not able to
maintain my forest as well as i need to.

but it was just one point of many.  help here would in most cases
likely be smething i have already thought of.  appreciates the offer.

next-error is a sort of general tool.  it is not just for this purpose
and compilation errors.  imo at least.  that is why c-c / uses it.

>
>> next-error would help me traverse and trim it rapidly.  i could
>> perhaps create a kb macro to emulate it, but i haven't tried yet.
>> then again, one could do so for grep mode etc. also.  :]
>
> If you decide to go with macro, it should not be too hard. Just  on
> agenda item, do your edits, macro-beg, switch to agenda buffer,
> next-line, , macro-end

yes :) [and doing soething to create canonical visibility at point so
that everything relevant is visible, and setting line in window].

[and finding that kb macro to lisp package and binding the command and
possibly overloading the next-error bindings.]

>
> Best,
> Ihor
>
>

my suggestion was for org's sake and i didn't think this much detail
would be needed at the time.  i used my computer use time to do the
best i could, but it seems that more detail was needed, and that
detail needed discussion.  my bad.

n.b.  i've been on the list for years, and many core features of org,
and parts thereof, were actually... my suggestions :).

but sometimes i miss the mark apparently, especially lately.  as in this case.

still, not sure why multiple grep buffers or grep with occur or c-c /,
etc. are compatible but multiple simultaneous agenda not so.

-- 
The Kafka Pandemic

A blog about science, health, human rights, and misopathy:
https://thekafkapandemic.blogspot.com



Re: next-error for agenda searches

2021-12-18 Thread Samuel Wales
another thing: it is an org consistency fr also, as in the outline c-c
/ does use next-match, and it would be good to have the same
capability among agenda results files, not merely in a single buffer.

On 12/18/21, Samuel Wales  wrote:
> btw, if anybody has difficulty understanding why i mention a bug or
> suggest a feature [such as why anbydoy would want it], please feel
> free to say so, otherwise i don't know that that is the case.  [please
> go easy on me though.]
>
> in this case, it is an emacs consistency fr.  across emacs, next-error
> goes from match to match, and it seems to me [perhaps i am mistaken]
> that agenda searches should be emacsy too.
>
> as for why it would be useful to me, so that i can get full context,
> with point at the match, thus 1] getting all the matches in my hands
> in the outline and 2] being able to edit immediately.
>
> furthermore, the next-closest thing, follow mode, puts point in wrong
> window.  also, 'canonical visibility is not present so i cannot see
> everything [this might or might not be fixable by user].
>
> also there is an accessibility issue with it.  i use large fonts so 2
> windows do not show much.  i use 2 windows only for very rare
> completion or selecting purposes.  not usable here.
>
> but i think it is an emacs consistency issue.  i agree with the
> frequently expressed idea that new features should be justified
> carefully, and next-error working as in e.g. grep seems right here.
>
> this isn't a huge deal for me at all, but e.g. when i do agenda
> searches i get really overwhelmed by the size and irrelevance
> [including duplication] of my own org forest developed over years.
>
> next-error would help me traverse and trim it rapidly.  i could
> perhaps create a kb macro to emulate it, but i haven't tried yet.
> then again, one could do so for grep mode etc. also.  :]
>
> On 12/14/21, Samuel Wales  wrote:
>> if you search for a regexp in a single org buffer, you can do
>> next-error to go to the next search.
>>
>> if you search in agenda, there is a mode where the match will show up
>> in the ohter window.  i find this inconvenient.
>>
>> there is no next-error to go to the next match for agenda searches.
>> or am i missing this feature someplace?  seems strange not to?
>>
>> such a thing would be consistent with c-c / / in an org buffer,
>> grep-mode, occur-mode, compilation-shell-minor-mode.  thanks!
>>
>> --
>> The Kafka Pandemic
>>
>> A blog about science, health, human rights, and misopathy:
>> https://thekafkapandemic.blogspot.com
>>
>
>
> --
> The Kafka Pandemic
>
> A blog about science, health, human rights, and misopathy:
> https://thekafkapandemic.blogspot.com
>


-- 
The Kafka Pandemic

A blog about science, health, human rights, and misopathy:
https://thekafkapandemic.blogspot.com



Re: next-error for agenda searches

2021-12-18 Thread Samuel Wales
btw, if anybody has difficulty understanding why i mention a bug or
suggest a feature [such as why anbydoy would want it], please feel
free to say so, otherwise i don't know that that is the case.  [please
go easy on me though.]

in this case, it is an emacs consistency fr.  across emacs, next-error
goes from match to match, and it seems to me [perhaps i am mistaken]
that agenda searches should be emacsy too.

as for why it would be useful to me, so that i can get full context,
with point at the match, thus 1] getting all the matches in my hands
in the outline and 2] being able to edit immediately.

furthermore, the next-closest thing, follow mode, puts point in wrong
window.  also, 'canonical visibility is not present so i cannot see
everything [this might or might not be fixable by user].

also there is an accessibility issue with it.  i use large fonts so 2
windows do not show much.  i use 2 windows only for very rare
completion or selecting purposes.  not usable here.

but i think it is an emacs consistency issue.  i agree with the
frequently expressed idea that new features should be justified
carefully, and next-error working as in e.g. grep seems right here.

this isn't a huge deal for me at all, but e.g. when i do agenda
searches i get really overwhelmed by the size and irrelevance
[including duplication] of my own org forest developed over years.

next-error would help me traverse and trim it rapidly.  i could
perhaps create a kb macro to emulate it, but i haven't tried yet.
then again, one could do so for grep mode etc. also.  :]

On 12/14/21, Samuel Wales  wrote:
> if you search for a regexp in a single org buffer, you can do
> next-error to go to the next search.
>
> if you search in agenda, there is a mode where the match will show up
> in the ohter window.  i find this inconvenient.
>
> there is no next-error to go to the next match for agenda searches.
> or am i missing this feature someplace?  seems strange not to?
>
> such a thing would be consistent with c-c / / in an org buffer,
> grep-mode, occur-mode, compilation-shell-minor-mode.  thanks!
>
> --
> The Kafka Pandemic
>
> A blog about science, health, human rights, and misopathy:
> https://thekafkapandemic.blogspot.com
>


-- 
The Kafka Pandemic

A blog about science, health, human rights, and misopathy:
https://thekafkapandemic.blogspot.com



Re: re created using regexp-opt fails in an org agenda command

2021-12-18 Thread Samuel Wales
[following on my most recent post] or for example this one, perhaps it
is too obscure but i wonder if these emaiuls will be seen again.

not really asking for anything.  just want to know if they go anyplace.  thank.s

On 12/12/21, Samuel Wales  wrote:
> this bug is strange because it appears as if regexp-opt is broken, but
> the only likely difference is an org upgrade via git clone.
>
> in an org agenda command, the same set of org todo kw works if a
> regexp was created using mapconcat, but not with regexp-opt.
>
> i expected that regexp-opt with 'words is identical to the mapconcat
> version in functionality in this context.
>
> ===
>
> i am trying to upgrade to recent org 9.5 main.  [goal is to eventually
> use bugfix branch with a couple of patches.]  [on main, however, i
> intend to first try the batch agenda archive speedups.  current is org
> 9.4.6.  thank you very very much for those.]
>
> i am running 25.1.1
> i used git clone from savannah to get the org repo
> i have not tried -Q yet as that woudl require a lot of setup
> i compiled with make which defaulted to make oldorg
>
> in my current versin of org, this bug does not exist, even though
> regexp-opt should not have changed.
>
> ===
>
> here is the org-agenda-custom-commands command.  i have provided some
> raw strings produced by the commands.
>
> this version errors with "and: Invalid regexp: "Unmatched ( or \\("".
> toggling backtrace on does not produce a backtrace.
>
> but if the regexp-opt is commented out and mapconcat is uncommented,
> it does not produce an error and it works.
>
> it also works with the string /produced by/ mapconcat.  but it still
> fails with the string produced by regexp-opt.  i confirmed that the
> string version of the regexp-opt works using re-search-forward, so idk
> why it would not work from one version of org.
>
> ("ne" "clean up by expired CLOSED"
>  tags (concat
>;; the + makes no difference seemingly
>"+CLOSED<\"<-1w>\"={^"
>;; "DONE"
>;; (alpha-org-todo-of--regexp :doneish)
>;; (apply #'append (mapcar #'alpha-org-todo-of
> '(:doneish)))
>(regexp-opt '("DONEKA" "DONE" "MOSTKA" "MOST"
> "ANYWAY" "DUPLICATEKA" "DUPLICATE" "MOOTKA" "MOOT" "WAKARANAI")
> 'words)
>;;
> "\\<\\(ANYWAY\\|D\\(?:ONE\\(?:KA\\)?\\|UPLICATE\\(?:KA\\)?\\)\\|MO\\(?:OT\\(?:KA\\)?\\|ST\\(?:KA\\)?\\)\\|WAKARANAI\\)\\>"
>;; (re-search-forward
> "\\<\\(ANYWAY\\|D\\(?:ONE\\(?:KA\\)?\\|UPLICATE\\(?:KA\\)?\\)\\|MO\\(?:OT\\(?:KA\\)?\\|ST\\(?:KA\\)?\\)\\|WAKARANAI\\)\\>")
> ;; this line works
>;; (mapconcat #'identity (apply #'append (mapcar
> #'alpha-org-todo-of '(:doneish))) "\\|")
>;; this line works
>;;
> "DONEKA\\|DONE\\|MOSTKA\\|MOST\\|ANYWAY\\|DUPLICATEKA\\|DUPLICATE\\|MOOTKA\\|MOOT\\|WAKARANAI"
>"$}")
>
> thanks.
>
> --
> The Kafka Pandemic
>
> A blog about science, health, human rights, and misopathy:
> https://thekafkapandemic.blogspot.com
>


-- 
The Kafka Pandemic

A blog about science, health, human rights, and misopathy:
https://thekafkapandemic.blogspot.com



Re: next-error for agenda searches

2021-12-18 Thread Samuel Wales
just curious whehter fr/bug/inconsistency emails drop off the end of
the org mailing list or whether they go on a todo list someplace.

i have others not responded to but can't keep track of them, but
that's ok.  i am grateful for the work done on org.  i realize this is
not a hight priority item, and possibly of no interest to others, and
everybody is a volunteer, etc.  not asking about that stuff.


On 12/14/21, Samuel Wales  wrote:
> if you search for a regexp in a single org buffer, you can do
> next-error to go to the next search.
>
> if you search in agenda, there is a mode where the match will show up
> in the ohter window.  i find this inconvenient.
>
> there is no next-error to go to the next match for agenda searches.
> or am i missing this feature someplace?  seems strange not to?
>
> such a thing would be consistent with c-c / / in an org buffer,
> grep-mode, occur-mode, compilation-shell-minor-mode.  thanks!
>
> --
> The Kafka Pandemic
>
> A blog about science, health, human rights, and misopathy:
> https://thekafkapandemic.blogspot.com
>


-- 
The Kafka Pandemic

A blog about science, health, human rights, and misopathy:
https://thekafkapandemic.blogspot.com



Re: Future TODOs with notes appear prematurely

2021-12-17 Thread Samuel Wales
a guess from everything yoyu described.  i assume you are talking
about the agenda agenda daily/weekly view.  please confirm.

what are the values of org-agenda-include-inactive-timestamps,
org-agenda-log-mode, and org-agenda-log-mode-items?


On 12/17/21, Colin Baxter   wrote:
> Hello,
>
> A TODO item scheduled for a future date ordinarily does not appear in
> today's agenda. However, this is not the case if the TODO has a note
> dated today in its log drawer. The TODO item is now visible in today's
> agenda, even though it's scheduled for the future. If this isn't a bug
> then how can I keep the TODO item hidden until its scheduled date?
>
> Best wishes,
>
> Colin Baxter.
>
>
>


-- 
The Kafka Pandemic

A blog about science, health, human rights, and misopathy:
https://thekafkapandemic.blogspot.com



next-error for agenda searches

2021-12-14 Thread Samuel Wales
if you search for a regexp in a single org buffer, you can do
next-error to go to the next search.

if you search in agenda, there is a mode where the match will show up
in the ohter window.  i find this inconvenient.

there is no next-error to go to the next match for agenda searches.
or am i missing this feature someplace?  seems strange not to?

such a thing would be consistent with c-c / / in an org buffer,
grep-mode, occur-mode, compilation-shell-minor-mode.  thanks!

-- 
The Kafka Pandemic

A blog about science, health, human rights, and misopathy:
https://thekafkapandemic.blogspot.com



re created using regexp-opt fails in an org agenda command

2021-12-12 Thread Samuel Wales
this bug is strange because it appears as if regexp-opt is broken, but
the only likely difference is an org upgrade via git clone.

in an org agenda command, the same set of org todo kw works if a
regexp was created using mapconcat, but not with regexp-opt.

i expected that regexp-opt with 'words is identical to the mapconcat
version in functionality in this context.

===

i am trying to upgrade to recent org 9.5 main.  [goal is to eventually
use bugfix branch with a couple of patches.]  [on main, however, i
intend to first try the batch agenda archive speedups.  current is org
9.4.6.  thank you very very much for those.]

i am running 25.1.1
i used git clone from savannah to get the org repo
i have not tried -Q yet as that woudl require a lot of setup
i compiled with make which defaulted to make oldorg

in my current versin of org, this bug does not exist, even though
regexp-opt should not have changed.

===

here is the org-agenda-custom-commands command.  i have provided some
raw strings produced by the commands.

this version errors with "and: Invalid regexp: "Unmatched ( or \\("".
toggling backtrace on does not produce a backtrace.

but if the regexp-opt is commented out and mapconcat is uncommented,
it does not produce an error and it works.

it also works with the string /produced by/ mapconcat.  but it still
fails with the string produced by regexp-opt.  i confirmed that the
string version of the regexp-opt works using re-search-forward, so idk
why it would not work from one version of org.

("ne" "clean up by expired CLOSED"
 tags (concat
   ;; the + makes no difference seemingly
   "+CLOSED<\"<-1w>\"={^"
   ;; "DONE"
   ;; (alpha-org-todo-of--regexp :doneish)
   ;; (apply #'append (mapcar #'alpha-org-todo-of '(:doneish)))
   (regexp-opt '("DONEKA" "DONE" "MOSTKA" "MOST"
"ANYWAY" "DUPLICATEKA" "DUPLICATE" "MOOTKA" "MOOT" "WAKARANAI")
'words)
   ;;
"\\<\\(ANYWAY\\|D\\(?:ONE\\(?:KA\\)?\\|UPLICATE\\(?:KA\\)?\\)\\|MO\\(?:OT\\(?:KA\\)?\\|ST\\(?:KA\\)?\\)\\|WAKARANAI\\)\\>"
   ;; (re-search-forward
"\\<\\(ANYWAY\\|D\\(?:ONE\\(?:KA\\)?\\|UPLICATE\\(?:KA\\)?\\)\\|MO\\(?:OT\\(?:KA\\)?\\|ST\\(?:KA\\)?\\)\\|WAKARANAI\\)\\>")
;; this line works
   ;; (mapconcat #'identity (apply #'append (mapcar
#'alpha-org-todo-of '(:doneish))) "\\|")
   ;; this line works
   ;;
"DONEKA\\|DONE\\|MOSTKA\\|MOST\\|ANYWAY\\|DUPLICATEKA\\|DUPLICATE\\|MOOTKA\\|MOOT\\|WAKARANAI"
   "$}")

thanks.

-- 
The Kafka Pandemic

A blog about science, health, human rights, and misopathy:
https://thekafkapandemic.blogspot.com



Re: Org-mode ASCII Export to support numbered references for links

2021-12-12 Thread Samuel Wales
you can also use inline footnotes.google[fn::https://google.com] which
will be exported like you like as a kludge if there is noe.

On 12/12/21, Samuel Wales  wrote:
> idk but you can put them in place using org-ascii-links-to-notes for a
> dry effect.
>
> On 12/12/21, Husain Alshehhi  wrote:
>> Org-mode's ascii export uses the link's description to create a reference
>> to
>> it at the end of the document. For example, a link to google will look
>> like
>> this:
>>
>> ,
>> | This is a [link to google].
>> |
>> | [link to google] <https://www.google.com>
>> `
>>
>> Is there a way to modify this behavior to using a number reference rather
>> than link description? Such as:
>>
>> ,
>> |
>> | This is a link to google[1].
>> |
>> | [1] <https://www.google.com>
>> `
>>
>> The reasoning behind this is that using numbers is more intuitive (as it
>> is
>> the common practice it plain text posts, emails etc.) Also, when there
>> are
>> two different links with the same description, the export is going to be
>> confusing to the reader. This happens when I use the description "link".
>>
>>
>>
>
>
> --
> The Kafka Pandemic
>
> A blog about science, health, human rights, and misopathy:
> https://thekafkapandemic.blogspot.com
>


-- 
The Kafka Pandemic

A blog about science, health, human rights, and misopathy:
https://thekafkapandemic.blogspot.com



Re: Org-mode ASCII Export to support numbered references for links

2021-12-12 Thread Samuel Wales
idk but you can put them in place using org-ascii-links-to-notes for a
dry effect.

On 12/12/21, Husain Alshehhi  wrote:
> Org-mode's ascii export uses the link's description to create a reference to
> it at the end of the document. For example, a link to google will look like
> this:
>
> ,
> | This is a [link to google].
> |
> | [link to google] 
> `
>
> Is there a way to modify this behavior to using a number reference rather
> than link description? Such as:
>
> ,
> |
> | This is a link to google[1].
> |
> | [1] 
> `
>
> The reasoning behind this is that using numbers is more intuitive (as it is
> the common practice it plain text posts, emails etc.) Also, when there are
> two different links with the same description, the export is going to be
> confusing to the reader. This happens when I use the description "link".
>
>
>


-- 
The Kafka Pandemic

A blog about science, health, human rights, and misopathy:
https://thekafkapandemic.blogspot.com



Re: Concrete suggestions to improve Org mode third-party integration :: an afterthought following Karl Voit's Orgdown proposal

2021-12-09 Thread Samuel Wales
i think the big change was v9.

On 12/9/21, Eric S Fraga  wrote:
> On Thursday,  9 Dec 2021 at 16:21, Russell Adams wrote:
>> Did Org break your Org editing experience in Emacs for your Org files,
>> or did this change just break some of the finer formatting details of
>> your exported Org file?
>
> It's been a while but, IIRC, the latter to a large extent; I should have
> been more clear.
>
> However, there have been changes in the past that affected the editing
> experience but I cannot remember if they were with v8 or v9 or somewhere
> in between, particularly dealing with locations of :LOGBOOK: and
> scheduling directives.  These happened when Nikolas cleaned up the
> parsing, to the benefit of org but at the cost of making some documents
> non-compliant.
>
> Nevertheless, as others have stated, given the stability provided by
> Emacs (parts of my .emacs date back to 1985!), and org being all text,
> even breaking changes are usually trivial to correct or adjust to.
>
> --
> : Eric S Fraga, with org release_9.5.1-243-gad53c5 in Emacs 29.0.50
> : Latest paper written in org: https://arxiv.org/abs/2106.05096
>
>


-- 
The Kafka Pandemic

A blog about science, health, human rights, and misopathy:
https://thekafkapandemic.blogspot.com



Re: Org-syntax: Intra-word markup

2021-12-05 Thread Samuel Wales
i think i can't add much useful to these threads, i agree with the
simplicity, but, a nuance, want for org to have had a bit more
consistency growing up.  e.g. quoting/escaping, demarcation, and
applicability of features in different contexts.

sort of a "mentally factored user interface" where the user's
expectation is pretty straightforwardly met.  e.g. works here so
should also work there.  or, there is only one rule for doing this.
that kind of thing.  orthogonality also.  few exceptions.

it is understandable in context that inconsistencies exist, and that
might apply to various maintenance-over-heavy things users want.

if we are to remove features as suggested below, then i suggest, where
possible, consistency be a desideratum for final result.


On 12/5/21, Russell Adams  wrote:
> On Sat, Dec 04, 2021 at 10:51:47AM +1100, Tim Cross wrote:
>>
>> Tom Gillespie  writes:
>>
>> > I don't mean to be a wet blanket...
>
> I'd like to be a wet blanket.
>
>> +infinity!
>>
>> Please, please can we stop trying to satisfy every edge case or extend
>> the markup to satisfy every possible scenario.
>
> +infinity^2
>
> I've often thought Org needs to hit the brakes and stop adding
> features, or cut out features that have a high support/maintenance
> cost. We need to respect our maintainers' time.
>
> --
> Russell Adamsrlad...@adamsinfoserv.com
>
> PGP Key ID: 0x1160DCB3   http://www.adamsinfoserv.com/
>
> Fingerprint:1723 D8CA 4280 1EC9 557F  66E8 1154 E018 1160 DCB3
>
>


-- 
The Kafka Pandemic

A blog about science, health, human rights, and misopathy:
https://thekafkapandemic.blogspot.com



Re: Removing obsolete function `org-truely-invisible-p'.

2021-12-04 Thread Samuel Wales
idk and will go along with whatever developers decide, but your note
was a good reminder that visible mode can be checked.

also made me wonder if it is possible to move anything from org-macs
out to topic-specific files like org-visibility.el or so?  no?

[idk what org visibility functions do what.  although i suspect org
can do it, i still use htmlize-buffer-substring-no-invisible.]


On 12/4/21, Karl Fogel  wrote:
> The function `org-truely-invisible-p' is defined in
> 'lisp/org-macs.el', but it is not used anywhere anymore in Org
> Mode, nor is it used anywhere in GNU Emacs (I checked on both
> 'emacs-28' branch and 'master' branch).
>
> The last (and possibly only?) call to that function was removed
> from `org-beginning-of-line' in this commit:
>
>   commit 3baf246f4f73005a4eacd7c368f7222f95d50243
>   Author: Nicolas Goaziou 
>   AuthorDate: Thu Apr 28 23:28:15 2016 +0200
>   Commit: Nicolas Goaziou 
>   CommitDate: Thu Apr 28 23:28:15 2016 +0200
>
>   Handle correctly `shift-select-mode'
>
>   * lisp/org.el (org-beginning-of-line): Handle correctly
>   `shift-select-mode'.
>
>   Reported-by: Mathieu Marques 
>   
>
> Then, a few months later in commit 87116700e6e, Nicholas moved the
> function to 'org-macs.el', where it has been sitting unused ever
> since.
>
> Should we just remove `org-truely-invisible-p'?  Or at least
> correct the spelling of its name ("truely" should be "truly")?
>
> It seems fairly unlikely to me that people are using it in their
> own code, although of course I cannot be sure of that.  Partly, I
> believe that because surely someone else would have noticed the
> misspelling by now, if enough people were using it :-).
>
> Best regards,
> -Karl
>
>


-- 
The Kafka Pandemic

A blog about science, health, human rights, and misopathy:
https://thekafkapandemic.blogspot.com



[fyi] extensible syntax, syntax features, parsing risk

2021-12-04 Thread Samuel Wales
the quoted post below, which had message id
20524da70901041233g105f372fv175a47dc9884f...@mail.gmail.com , starts a
thread relevant to the current discussion of syntax, at least
historically, maybe practically.  could not find it online.

there were succeeding threads with examples and other stuff for id
markers and graph-theoretic things and other examples, where you as
user could always use a cl-like syntax [i.e. something like
"$[functionality-name arg :keyword arg]"].  my main concern was the
proliferation of syntax, and the risks of that [e.g. parsing] and
wanting the ability of factoring of syntax features.

display, parsing and so on would be shared [factored] among all the
different such features; org would always handle that the same.  thus
as a user even, you could add some new feature in lisp, and write it
in org using this syntax.  it would already work.

i have more in notes.  idk if it is still relevant, but i have
included the thread starter for the earliest thread [carsten/myself].

On 1/4/09, Samuel Wales  wrote:
> A general idea, which might or might not be useful.
>
> There are occasionally questions about syntax, like this:
>
>   Also, I'm afraid definition matching regexp won't play
>   nicely with text indentation, ... -- Paul
>
> Or this:
>
>   What would be safer?  -- Carsten
>
> I like the footnote implementation, so this is for future
> features, not necessarily footnotes.
>
> One issue when implementing new syntax (or changing existing
> syntax or cleaning up code) is parsing risk, which I will
> define as the risk that the syntax and the regexp or
> matching code:
>
>   1) conflicts with user text
>   2) conflicts with existing features
>   3) will be hard to maintain
>   4) constrains future features by making them conflict
>  syntactically
>   5) makes you run out of syntax to use in the future
>   6) will require complicated regexps
>   7) doesn't readily handle stuff you might want in the
>  future, like being combined with another feature
>   8) will be hard to quote, escape, comment, *boldify*, etc.
>   9) doesn't handle nestability, print-readability,
>  pretty-printability, syntax coloring, etc.
>   10) will be inefficient when called in a loop
>   11) isn't factored out
>   12) etc.
>
> For example, one of the many reasons for using org-IDs (:))
> in the conversation manager (as proposed) is that there are
> already functions to parse org-IDs, so a new syntax is not
> necessary and therefore parsing risk is minimized.
>
> In case parsing risk is a concern when adding a new feature
> to org, here is one idea: have a generic syntax that is
> extensible with keywords.
>
> The idea is to have a bracketing syntax with a reserved
> keyword as the first element that says what you are doing.
>
> To use footnotes as an example (this is not a suggestion to
> change footnote syntax, just an example that can be used for
> future syntax):
>
> You might use something like "here is some text to be
> footnoted $[fn apple]" to specify the footnote link, and
> "$[fn-target apples are delicious]" to specify the target.
>
> The general point I want to make is that once such a syntax
> is decided on, many future features are possible without
> introducing parsing risk.
>
> For example, you can implement a new feature as
> "$[my-new-feature ...]".  Then there is no parsing risk,
> even though you have just added a new feature.
>
> For modifications of features, you can use keywords:
> "$[my-new-feature ... :myparameter ...]".  These are easily
> parsed by standard functions for parsing lists.
>
> You can develop ways to boldify, quote, nest, prettily
> print, etc. this syntax, and those ways will work well with
> all future features that use it.
>
> Of course, the dollar sign and brackets are not the only
> possibility; it could be percent sign and parentheses, for
> example.
>
> You will not be starting from scratch.  Lisp has already
> worked out many of these issues.
>
> I will leave it to those who write massive amounts of org
> code to decide whether an extensible syntax might be useful
> to reduce parsing risk for future features.
>
> But I thought that I would propose the idea in case it is of
> interest.
>
> --
> For personal gain, myalgic encephalomyelitis denialists are knowingly
> causing further suffering and death by grossly corrupting science.  Do
> you care about the world?
> http://www.meactionuk.org.uk/What_Is_ME_What_Is_CFS.htm
>


-- 
The Kafka Pandemic

A blog about science, health, human rights, and misopathy:
https://thekafkapandemic.blogspot.com



Re: Org-syntax: Intra-word markup

2021-12-02 Thread Samuel Wales
a silly question.  don't we already use something kinda similar to
\emph{what}ever for all backends?  could we do so?

On 12/2/21, Denis Maier  wrote:
> Am 02.12.2021 um 19:11 schrieb Tom Gillespie:
>> I don't mean to be a wet blanket, but the edge cases for
>> the current markup syntax are already hard enough to
>> implement correctly, to the point where different parts of
>> Org mode are inconsistent. Intra-word markup isn't viable
>> because there simply isn't any sane way to parse something
>> like *hello world*/hrm/oh no*. The other issue is that this will
>> degrade parsing performance because almost every
>> character could precede the start of a markup section.
>>
>> I recommend anyone suggesting solutions try to implement
>> something that can parse the markup unambiguously with
>> lots of nasty test cases. You will likely find that it is impossible
>> to consistently tokenize markup, and that you have to hand
>> write a whole bunch of heuristics, making Org syntax even
>> harder to implement correctly.
>>
>> Any solution that suggests extending how =/*~+_  can be
>> used gets a hard no from me. I could see teaching other
>> exporters how to interpret \emph{hello}world, but trying for
>> to have any sane behavior for something like
>> why *hello*world oh no a wild askterisk*
>> is not worth it.
>
> As I've said before, I could well live with \emph{what}ever or something
> similar.
>
> Denis
>
>


-- 
The Kafka Pandemic

Please learn what misopathy is.
https://thekafkapandemic.blogspot.com/2013/10/why-some-diseases-are-wronged.html



Re: [PATCH] org.el: Fix the filling of regions containing lists

2021-11-30 Thread Samuel Wales
wow thank you i look forward to this.

On 11/30/21, Sébastien Miquel  wrote:
> Hi,
>
> The attached patch fixes the following issues with the functions
> =fill-region= and =fill-paragraph=, when called with an active region
> containing a list.
>
> In the examples, replace 'long line' by long lines to be filled.
>
>   + Calling =fill-region= on a region which contains a list with single
>     line items (such as the one below) breaks the list structure.
>     - long line
>     - long line
>   + Calling =fill-region= on a region with a list such as the one below
>     doesn't fill the list
>     - short line
>   short line
>     - short line
>   short line
>   + Calling =fill-paragraph= on a region containing a list such as the
>     one below doesn't fill the first item
>     - long line
>     - long line
>     - long line
>   + Calling =fill-paragraph= on a region containing a list such as the
>     one below doesn't fill the list
>     - long line
>     - long line
>     - short line
>
> Regards,
>
> --
> Sébastien Miquel
>


-- 
The Kafka Pandemic

Please learn what misopathy is.
https://thekafkapandemic.blogspot.com/2013/10/why-some-diseases-are-wronged.html



Re: "Orgdown", the new name for the syntax of Org-mode

2021-11-30 Thread Samuel Wales
um, or just "assuming too much bias"?  :]

again i don't think you are really doing these things by just
proposing a bunch of ideas about markup languages.  not everybody
knows all languages and you'll get substantive corrective feedback.

On 11/30/21, Samuel Wales  wrote:
> if you will forgive one more bikeshed answer, what about this?
>
> - reduced org
> - reduced org, version 1
>
> and maybe
>
> - .rorg extension [if and only if needed to guarantee reduction]
>
> as for why you got bikeshed answers, maybe the subject header of this
> thread might have been part of it?
>
> idk.
>
> ===
>
> as for [other thread], i don't think you are doing this because
> reduced org is an interesting idea but:
>
>> "Does "assuming too much on other people's world because on my own small
>> world" have a scientific name?"
>
> "epistemic tresspassing" has been used for something a bit similar.
> also i would use the term "drive-by paper" for e.g. making claims
> about a disease that the authors do not understand at all but think
> they do, wanting to try their ideology, measurement tool, or intuition
> regardless so they can get a paper out of it, but that does not apply
> here.  more generally are things like fiefdom/chauvanism, ideological
> bias, and professional bias, which are different.  maybe there should
> be a "small world bias" or an "if you have a hammer everything looks
> like a nail bias"?  and a "common belief bias" and "cultural belief
> bias"?  and a "my favorite language bias"?  you might also consider
> the availability heuristic, saliency bias, epistemic injustice, and
> omission bias, but those are different too.
>
> i think it is a good idea to be interested in the possibility of
> reduced org as a generic markup language.
>
> On 11/28/21, Karl Voit  wrote:
>> Hi Org-mode community,
>>
>> At this year's EmascsConf, I had a 12 minute video where I explain why
>> we do need a different name for the syntax of Org-mode in contrast to
>> the Elisp implementation of GNU/Emacs Org-mode.
>>
>> I would like you to read my rationale and motivate you to use the term
>> "Orgdown" for the syntax and "Orgdown1" for the first (very basic)
>> level of Orgdown syntax elements.
>>
>> - The EmacsConf21 talk: https://emacsconf.org/2021/talks/org-outside
>> - Orgdown site: https://gitlab.com/publicvoit/orgdown (please
>> contribute!)
>> - My motivation article: https://karl-voit.at/2021/11/27/orgdown/
>>   - This is the longer version of my 12 minute EmacsConf21 video.
>> - My personal copy of the video:
>> https://tube.graz.social/w/bgJVfjPLQAoJwLJQZoo3Hu
>>
>>
>> Just as a sneak preview (not as a replacement for my motivation article):
>>
>> Orgdown is and will be defined in a set of levels, starting with very
>> basic Orgdown1 (or OD1 or O↓1 or ⧬1 - depending on your coolness
>> factor of choice :-) )
>>
>> - OD1 →
>> https://gitlab.com/publicvoit/orgdown/-/blob/master/doc/Orgdown-Levels.org
>> - OD2 → will be defined in future
>> - OD3 → will be defined in future
>> - ...
>> - OD∞ = Org-mode (by definition)
>>
>> Any OD-level needs to be compatible with Org-mode as implemented in
>> Elisp for GNU/Emacs Org-mode according to https://orgmode.org. Any ODx
>> is a sub-set of the syntax elements of ODy (with y>x).
>>
>> With introducing a new term specific for the syntax, we do get the
>> benefit of getting a better way to handle Org-mode support in
>> 3rd-party tools such as listed on
>> https://gitlab.com/publicvoit/orgdown/-/blob/master/doc/Tool-Support.org
>> (please extend!).
>>
>> Having a well-defined sub-set of Org-mode, I also do think that formal
>> definitions of the Org-mode syntax will be easier to develop, starting
>> with the very simple OD1 level.
>>
>> It would be awesome if we start referring to syntax support in
>> 3rd-party tools with the corresponding OD levels.
>>
>> I want to emphasize that the goal of Orgdown is NOT and will never be
>> something that is an alternative to our golden standard Org-mode. We
>> will try hard not to get into the Markdown situation where you need to
>> know the exact flavor of the markup in order to produce text.
>>
>> So far, the response was great at the conference and I do hope that
>> this idea will get a life of its own, developing the standard further,
>> bringing this magnificent lightweight markup to the digital world.
>> This also eases some pain for users of GNU/Emacs when it comes to
>> exchanging text-based data.
>>
>> Thanks for your support here!
>>
>>
>> --
>> Personal Information Management > http://Karl-Voit.at/tags/pim/
>> Emacs-related > http://Karl-Voit.at/tags/emacs/
>>
>>
>>
>
>
> --
> The Kafka Pandemic
>
> Please learn what misopathy is.
> https://thekafkapandemic.blogspot.com/2013/10/why-some-diseases-are-wronged.html
>


-- 
The Kafka Pandemic

Please learn what misopathy is.
https://thekafkapandemic.blogspot.com/2013/10/why-some-diseases-are-wronged.html



Re: "Orgdown", the new name for the syntax of Org-mode

2021-11-30 Thread Samuel Wales
if you will forgive one more bikeshed answer, what about this?

- reduced org
- reduced org, version 1

and maybe

- .rorg extension [if and only if needed to guarantee reduction]

as for why you got bikeshed answers, maybe the subject header of this
thread might have been part of it?

idk.

===

as for [other thread], i don't think you are doing this because
reduced org is an interesting idea but:

> "Does "assuming too much on other people's world because on my own small 
> world" have a scientific name?"

"epistemic tresspassing" has been used for something a bit similar.
also i would use the term "drive-by paper" for e.g. making claims
about a disease that the authors do not understand at all but think
they do, wanting to try their ideology, measurement tool, or intuition
regardless so they can get a paper out of it, but that does not apply
here.  more generally are things like fiefdom/chauvanism, ideological
bias, and professional bias, which are different.  maybe there should
be a "small world bias" or an "if you have a hammer everything looks
like a nail bias"?  and a "common belief bias" and "cultural belief
bias"?  and a "my favorite language bias"?  you might also consider
the availability heuristic, saliency bias, epistemic injustice, and
omission bias, but those are different too.

i think it is a good idea to be interested in the possibility of
reduced org as a generic markup language.

On 11/28/21, Karl Voit  wrote:
> Hi Org-mode community,
>
> At this year's EmascsConf, I had a 12 minute video where I explain why
> we do need a different name for the syntax of Org-mode in contrast to
> the Elisp implementation of GNU/Emacs Org-mode.
>
> I would like you to read my rationale and motivate you to use the term
> "Orgdown" for the syntax and "Orgdown1" for the first (very basic)
> level of Orgdown syntax elements.
>
> - The EmacsConf21 talk: https://emacsconf.org/2021/talks/org-outside
> - Orgdown site: https://gitlab.com/publicvoit/orgdown (please contribute!)
> - My motivation article: https://karl-voit.at/2021/11/27/orgdown/
>   - This is the longer version of my 12 minute EmacsConf21 video.
> - My personal copy of the video:
> https://tube.graz.social/w/bgJVfjPLQAoJwLJQZoo3Hu
>
>
> Just as a sneak preview (not as a replacement for my motivation article):
>
> Orgdown is and will be defined in a set of levels, starting with very
> basic Orgdown1 (or OD1 or O↓1 or ⧬1 - depending on your coolness
> factor of choice :-) )
>
> - OD1 →
> https://gitlab.com/publicvoit/orgdown/-/blob/master/doc/Orgdown-Levels.org
> - OD2 → will be defined in future
> - OD3 → will be defined in future
> - ...
> - OD∞ = Org-mode (by definition)
>
> Any OD-level needs to be compatible with Org-mode as implemented in
> Elisp for GNU/Emacs Org-mode according to https://orgmode.org. Any ODx
> is a sub-set of the syntax elements of ODy (with y>x).
>
> With introducing a new term specific for the syntax, we do get the
> benefit of getting a better way to handle Org-mode support in
> 3rd-party tools such as listed on
> https://gitlab.com/publicvoit/orgdown/-/blob/master/doc/Tool-Support.org
> (please extend!).
>
> Having a well-defined sub-set of Org-mode, I also do think that formal
> definitions of the Org-mode syntax will be easier to develop, starting
> with the very simple OD1 level.
>
> It would be awesome if we start referring to syntax support in
> 3rd-party tools with the corresponding OD levels.
>
> I want to emphasize that the goal of Orgdown is NOT and will never be
> something that is an alternative to our golden standard Org-mode. We
> will try hard not to get into the Markdown situation where you need to
> know the exact flavor of the markup in order to produce text.
>
> So far, the response was great at the conference and I do hope that
> this idea will get a life of its own, developing the standard further,
> bringing this magnificent lightweight markup to the digital world.
> This also eases some pain for users of GNU/Emacs when it comes to
> exchanging text-based data.
>
> Thanks for your support here!
>
>
> --
> Personal Information Management > http://Karl-Voit.at/tags/pim/
> Emacs-related > http://Karl-Voit.at/tags/emacs/
>
>
>


-- 
The Kafka Pandemic

Please learn what misopathy is.
https://thekafkapandemic.blogspot.com/2013/10/why-some-diseases-are-wronged.html



Re: bulk archive slow

2021-11-23 Thread Samuel Wales
thank you!  bulk archiving will be among the first things i will try
once i upgrade.  i have years[?] of doneified tasks now i think.

i always use maint, with my own few patches rebased on top, so not
sure if i can take advantage of it, except to run main to do it.

still will be highly useful.  i ahve kept these improvements to bulk
archving in mind as i consier upgrading.


this brings up a tangential question.  what was the reasoning behind
changing maint to bugfix and master to main?




On 11/23/21, Ihor Radchenko  wrote:
> Samuel Wales  writes:
>
>> in recent maint, bulk archive is slow for me.  not a huge deal but
>> org-element--current-element takes up 92 percent of cpu time in
>> profiler.  6 entries took a few minutes.  this is just a heads up in
>> case anybody can confirm.
>
> Just a note that bulk archiving should be a lot faster on latest main.
>
> Best,
> Ihor
>


-- 
The Kafka Pandemic

Please learn what misopathy is.
https://thekafkapandemic.blogspot.com/2013/10/why-some-diseases-are-wronged.html



Re: org-sort random

2021-11-23 Thread Samuel Wales
if random sorting of siblings is useful, another entry in the sorting
menu, dedicated to it, would eliminate any issues with completion.

it is a clever idea to feed random to sort by function.  maybe some
won't catch the connection.  just a possibility.  not trying to bloat.

On 11/23/21, Vikas Rawal  wrote:
>>
>>
>> I think that depends on the completion framework.  With the default
>> completion, yes, I think RET should do it.  With ivy, it's instead
>> ivy-immediate-done (C-M-j).  I'm not sure offhand about other
>> frameworks.
>>
>>
> That's what it needed. Thanks.
>
> I wonder if there would be a better way to document this somewhere so that
> people using different completion frameworks could figure out how to do it.
> It seems to be something that would be useful to others.
>
> Thanks again
>
> Vikas
>


-- 
The Kafka Pandemic

Please learn what misopathy is.
https://thekafkapandemic.blogspot.com/2013/10/why-some-diseases-are-wronged.html



Re: org-sort random

2021-11-23 Thread Samuel Wales
i have found or would find random line within buffer or region to be
useful, and also random entry in org agenda files.

i'd find this useful too, but i think i'd find it more useful to keep
the ordering the same but instead go to a random entry within region.

On 11/23/21, Samuel Wales  wrote:
> if random sorting of siblings is useful, another entry in the sorting
> menu, dedicated to it, would eliminate any issues with completion.
>
> it is a clever idea to feed random to sort by function.  maybe some
> won't catch the connection.  just a possibility.  not trying to bloat.
>
> On 11/23/21, Vikas Rawal  wrote:
>>>
>>>
>>> I think that depends on the completion framework.  With the default
>>> completion, yes, I think RET should do it.  With ivy, it's instead
>>> ivy-immediate-done (C-M-j).  I'm not sure offhand about other
>>> frameworks.
>>>
>>>
>> That's what it needed. Thanks.
>>
>> I wonder if there would be a better way to document this somewhere so
>> that
>> people using different completion frameworks could figure out how to do
>> it.
>> It seems to be something that would be useful to others.
>>
>> Thanks again
>>
>> Vikas
>>
>
>
> --
> The Kafka Pandemic
>
> Please learn what misopathy is.
> https://thekafkapandemic.blogspot.com/2013/10/why-some-diseases-are-wronged.html
>


-- 
The Kafka Pandemic

Please learn what misopathy is.
https://thekafkapandemic.blogspot.com/2013/10/why-some-diseases-are-wronged.html



Re: c47b535bb origin/main org-element: Remove dependency on ‘org-emphasis-regexp-components’

2021-11-17 Thread Samuel Wales
i think i found it useful, long ago, when it was ok/tolerated to
change the var, and probably still, to /"do this"/ and /this,/.

although the latter seems weird to me now so i must not now understand
what i was doing.

i think changing the var was at least in a faq or on worg or so, so it
might be needed to compare user's value with standard-value.


On 11/17/21, Max Nikulin  wrote:
> On 17/11/2021 04:56, Samuel Wales wrote:
>> might be useful to know whether a default regexp change could satisfy
>> everybody?  in my case i remove " and , from third re.
>
> Samuel, I have seen your next message, but it still may be helpful to
> have an example (for a case if you will meet the problem again).
>
> These regexps will always fail under some conditions, since it is not
> strict markup. An example is emphasis terminated inside link target
>
> /A link [[https://orgmode.org/?oops=true][Org Mode]]
>
> On 16/11/2021 14:43, Ihor Radchenko wrote:
>> Max Nikulin writes:
>>
>>> Better docs and some restriction on defcustom values were discussed
>>> earlier:
>>> https://list.orgmode.org/87k0oyd3pw@nicolasgoaziou.fr/
>>> Nicolas Goaziou. Re: Using backticks for the inline code delimeter? Mon,
>>> 19 Apr 2021 11:27:07 +0200
>>>
>>> Sorry, I have not prepared a patch. I am not confident with defcustom
>>> fine tuning and have not experimented with it since that time.
>>
>> Maybe something like the attached?
>
> Thank you, Ihor. Another reason why I have not tried to do it myself is
> that it is necessary to test behavior for users who customized markers.
> The change should not be fatal for them. I have not checked it with you
> patch yet.
>
> I was considering some way to warn users if improper customization is
> detected (unexpected marker is noticed). It should be noticeable to make
> user aware of export issues but not too annoying.
>
>> +The characters in the alist must not be changed.  They do not affect
>> +the actual Org syntax, just fontification.
>
> Since this is known point of abuses, maybe stronger words are appropriate.
>
> Do not change makers and do not add new ones to use custom markers for
> existing styles or to introduce new styles. Org syntax is not meant to
> be configurable and such modifications will not work with export. If you
> are interested in fontification of custom markup inside Emacs only,
> there are other ways to achieve desired effect.
>
> In addition, I do not like the following phrase in the manual:
>
>> To narrow down the list of available markup syntax, you can customize
>> org-emphasis-alist.
>
>
>


-- 
The Kafka Pandemic

Please learn what misopathy is.
https://thekafkapandemic.blogspot.com/2013/10/why-some-diseases-are-wronged.html



Re: c47b535bb origin/main org-element: Remove dependency on ‘org-emphasis-regexp-components’

2021-11-16 Thread Samuel Wales
i should point out that my changes are old and i don't know if they
have already been done

On 11/16/21, Samuel Wales  wrote:
> hmm i will have to try not setting o-e-r-c [ordinary user].  probably
> a lot of users do.
>
> might be useful to know whether a default regexp change could satisfy
> everybody?  in my case i remove " and , from third re.  i also have a
> note "org-set-emph-re is what you are supposed to use, but it is
> undocumented".  for some reason.  that might be obsolete,
>
>
> On 11/16/21, Ihor Radchenko  wrote:
>> Max Nikulin  writes:
>>
>>> Better docs and some restriction on defcustom values were discussed
>>> earlier:
>>> https://list.orgmode.org/87k0oyd3pw@nicolasgoaziou.fr/
>>> Nicolas Goaziou. Re: Using backticks for the inline code delimeter? Mon,
>>> 19 Apr 2021 11:27:07 +0200
>>>
>>> Sorry, I have not prepared a patch. I am not confident with defcustom
>>> fine tuning and have not experimented with it since that time.
>>
>> Maybe something like the attached?
>>
>> Best,
>> Ihor
>>
>>
>
>
> --
> The Kafka Pandemic
>
> Please learn what misopathy is.
> https://thekafkapandemic.blogspot.com/2013/10/why-some-diseases-are-wronged.html
>


-- 
The Kafka Pandemic

Please learn what misopathy is.
https://thekafkapandemic.blogspot.com/2013/10/why-some-diseases-are-wronged.html



Re: c47b535bb origin/main org-element: Remove dependency on ‘org-emphasis-regexp-components’

2021-11-16 Thread Samuel Wales
hmm i will have to try not setting o-e-r-c [ordinary user].  probably
a lot of users do.

might be useful to know whether a default regexp change could satisfy
everybody?  in my case i remove " and , from third re.  i also have a
note "org-set-emph-re is what you are supposed to use, but it is
undocumented".  for some reason.  that might be obsolete,


On 11/16/21, Ihor Radchenko  wrote:
> Max Nikulin  writes:
>
>> Better docs and some restriction on defcustom values were discussed
>> earlier:
>> https://list.orgmode.org/87k0oyd3pw@nicolasgoaziou.fr/
>> Nicolas Goaziou. Re: Using backticks for the inline code delimeter? Mon,
>> 19 Apr 2021 11:27:07 +0200
>>
>> Sorry, I have not prepared a patch. I am not confident with defcustom
>> fine tuning and have not experimented with it since that time.
>
> Maybe something like the attached?
>
> Best,
> Ihor
>
>


-- 
The Kafka Pandemic

Please learn what misopathy is.
https://thekafkapandemic.blogspot.com/2013/10/why-some-diseases-are-wronged.html



Re: add automatically a counter to a header/TODO???

2021-11-03 Thread Samuel Wales
idk if this is useful, but i was thinking of doing something similar,
except, automatically for the purpose of recording progress.

as in, the number of times i did something to the task.  in tags not
properties, thus on the header.  like :n_2:

i tried keywords for progress instead, but that is coarse [cannot
"reward" tiny progress] and requires decision making -- is this
started or progressed?  that can be too much cognitive overhead for
me.  should i really be deciding if it has progressed?

also design decisions --- should i sort up or down by progress kw?
up makes more progressed more visible, but usually one puts more
progressed downward [e.g. doneish is toward bottom].  and
too ugly if they are unsorted, with mixed keywords.

so i thought, what if i could just have, say, started, and then, to
increment the counter, i change the keyword to itself, started.

i don't have the capacity to implement this, and i'm not sure it's
what i want, but maybe the change to itself idea is useful.


On 11/3/21, Uwe Brauer  wrote:
 "ESF" == Eric S Fraga  writes:
>
>> On Monday,  1 Nov 2021 at 20:53, Uwe Brauer wrote:
>>> (format "%s" (- 1 (string-to-number
>
>> Shouldn't this be the other way around, i.e.
>> (- (string-to-number ...) 1)
>> ?
>
> Oops you are right, thanks
>


-- 
The Kafka Pandemic

Please learn what misopathy is.
https://thekafkapandemic.blogspot.com/2013/10/why-some-diseases-are-wronged.html



pretty basic upgrade questions

2021-10-20 Thread Samuel Wales
haven't upgraded from maint.  have changes that automatically rebase
on top of upstream org.  currently run make oldorg.

is git clone best, to clean up tags etc.?  then i use git branch
bugfix, then kinda try to figure out rebasing, and use make, not
oldorg?

also, i'm not sure if the manual's make autoloads is necessary if you
do make.  maybe that could be clarified in the manual?

also, the manual says you can "create a local configuration with ‘make
config", but doesn't specify.  what is a configuration?



Re: org-persist

2021-10-20 Thread Samuel Wales
On 10/19/21, Ihor Radchenko  wrote:
> enabled all the time in future.  If you have specific reasons to avoid
> org-element-cache, may you share them?

fwiw, long ago, i disabled org element cache due to buffer corruption.
perhaps that has been fixed and tested.

also i presume this is all on main not bugfix [i haven't upgraded
maint yet; first thing i will do is try the archiving improvement].



Re: nbsp as blank

2021-10-19 Thread Samuel Wales
there exists org-emphasis-regexp-components, fwiw.

On 10/19/21, Alexandre Garreau  wrote:
> Hello,
>
> nbsp (non-breaking space, #xA0) is not recognized as blank in org-mode,
> such that “*text* :” (it’s a nbsp here) doesn’t recognize as emphasized…
>
> I recall a variable containing such characters but can’t find it again,
> does anyone know? the manual seems large and that looks non-obvious to find
>
> quickly…
>
>


-- 
The Kafka Pandemic

Please learn what misopathy is.
https://thekafkapandemic.blogspot.com/2013/10/why-some-diseases-are-wronged.html



[BUG) filling bullet list

2021-09-29 Thread Samuel Wales
I have tried this with -Q in Emacs 25 and recent Org maint.  Also with
my usual setup.  I have not tested the Org released today.

I frequently try to fill bullet lists, where items are longer than fill column.

- mark the list using set-mark-command and movement.  [hre is
something to mke the item long asnd fkajsd nfkja nsdkjfn aksjdnf
kajsnd fkajsn dkfjan skdjn faksjdn fkjad nsfkjanaksj dnfkja sdkfjna
ksdjf kajsd fkjas dkfjna skdjf akjsdnf kajnsdkfjansk djfn.]
- run org-fill-paragraph interactively
- expect each item to be filled
- no filling occurs

In the past I used filladapt.el, but I think its time has mostly gone.
I still try it from time to time, such as email quotes, but it is
unloaded.  I have tried other Emacs fill functions, but I either get
no filling or the whole list becomes one paragraph.

fill-paragraph-function is a variable defined in ‘fill.el’.
Its value is ‘org-fill-paragraph’
Local in buffer executive--a.org; global value is nil

-- 
The Kafka Pandemic

Please learn what misopathy is.
https://thekafkapandemic.blogspot.com/2013/10/why-some-diseases-are-wronged.html



Re: Bug: Org mode fails to compile using Emacs 24.5-r10

2021-09-28 Thread Samuel Wales
in debian lts stretch, which goes to June 30, 2022, there is both with
24 being the default.  there are a bunch of packages made into debian
packages.  idk if they work with both.


On 9/28/21, Max Nikulin  wrote:
> On 28/09/2021 12:33, Bastien wrote:
>> Tim Cross writes:
>>
>>> I do think it is probably time to drop support for Emacs 24 in the next
>>> major release. However, we cannot drop it 'mid release'.
>>
>> I've added a section called "Compatibility with Emacs versions" on
>> this page: https://orgmode.org/worg/org-maintenance.html
>>
>> We now make it clear that latest Org stable aims at being compatible
>> with Emacs current stable, and the two previous one.
>>
>> That is: Org 9.4.6 is compatible with 27.x, 26.x and 25.x but maybe
>> not with 24.x (24.1 being 9 years old now).
>
> lisp/org.el:;; Package-Requires: ((emacs "24.3"))
>
> Should not it be updated?
>
> https://orgmode.org/worg/org-maintenance.html:
>> For example, if the current major version of Emacs is 28.x, then the
>> latest stable version of Org should be compatible with Emacs 28.x, 27.x
>> and 26.x – but not with Emacs 25.x.
>
> Ubuntu-18.04 bionic is a Long Time Support release (April 2018),
> emacs-25.2.2 provided from system repository. Maybe it should be
> supported even though next LTS release Ubuntu-20.04 focal is available.
>
>
>


-- 
The Kafka Pandemic

Please learn what misopathy is.
https://thekafkapandemic.blogspot.com/2013/10/why-some-diseases-are-wronged.html



Re: Org branches: master, main, and maint?

2021-09-26 Thread Samuel Wales
i have forgotten all my non-basic git, so i guess i am in for a bunch
of figuring out the automatic rebase of my stuff on top of upstream.

perhaps i can do a single git clone, do the rebase, and then change
branches to create the ohters.  but i presume this is a normal git
thing git clone to get rid of stuff lying around, deal with tags, and
deal with branches?

if there is documentation perhaps say that bugfix ~= stable?


On 9/26/21, Max Nikulin  wrote:
> On 26/09/2021 17:31, Bastien wrote:
>> Timothy writes:
>>
>>> I’ve just had a look at the branches, and I see that we currently
>>> have
>>>
>>>  master
>>>  main
>>>  maint
>>
>> You probably listed your local branch with "git branch -a" or by
>> checking your .git/config file.
>>
>> If you clone a fresh repo like this:
>>
>> ~$ git clone https://git.savannah.gnu.org/git/emacs/org-mode.git
>>
>> and fetch all the branches (git fetch --all) you should only see
>> the three branches mentioned above.
>
>  git fetch --prune
>
> might help to keep personal local branches but to remove non-existing
> remote ones if you changed URL of origin repository. I renamed old
> "origin" and added new one with savannah URL, so each repository has its
> own branch (That is why I may be a bit wrong concerning exact behavior
> of --prune in this case).
>
>
>


-- 
The Kafka Pandemic

Please learn what misopathy is.
https://thekafkapandemic.blogspot.com/2013/10/why-some-diseases-are-wronged.html



Re: toggle-truncate-lines outside table and source regions

2021-09-23 Thread Samuel Wales
almost as if truncate line feature should be a text property?  good
idea to take up with devs if no solution arrives.  source blocks have
c-c '; idk about tables.  perhaps you could at least have ugliness in
the outline but correctness in editing.

On 9/23/21, Bill Burdick  wrote:
> Gah, sorry about that -- I didn't read your message carefully enough!
>
>
> -- Bill
>
>
> On Thu, Sep 23, 2021 at 4:56 AM Luca Ferrari  wrote:
>
>> On Wed, Sep 22, 2021 at 3:49 PM Bill Burdick 
>> wrote:
>> >
>> > How about adding
>> >
>> > (lambda () (toggle-truncate-lines 1))
>> >
>> > to org-mode-hooks in your EMACS init file?
>>
>> isn't this the same as M-x toggle-truncate-lines ? Because it will
>> truncate every line, but I'm searching for a way to truncate only
>> text, and not tables nor code.
>> AM I misunderstanding your suggestion?
>>
>> Luca
>>
>


-- 
The Kafka Pandemic

Please learn what misopathy is.
https://thekafkapandemic.blogspot.com/2013/10/why-some-diseases-are-wronged.html



Re: [PATCH] Improve org-mouse support for checkboxes

2021-09-18 Thread Samuel Wales
thanks for this.  if tests are written, might be useful to include the
case where half-checked are parents.

On 9/18/21, Jim Porter  wrote:
> While trying out `org-mouse', I noticed two semi-related issues with
> checkboxes. First, intermediate-state checkboxes (like [-]) aren't
> clickable. Second, if the checkboxes are inside a block and the theme
> gives the block a background color, the block's background is removed
> behind the checkbox. To see both of these in action:
>
>$ cat file.org
>* Regular
>- [X] Checked.
>- [-] Half-checked.
>- [ ] Not checked.
>* In block
>#+begin_src org
>- [X] Checked.
>- [-] Half-checked.
>- [ ] Not checked.
>#+end_src
>
>$ emacs -Q --eval '(progn (setq org-modules '"'"'(org-mouse))
> (custom-set-faces '"'"'(org-block ((t :background "green")' file.org
>
> The attached patch fixes both of these issues. For the first problem,
> maybe it would be useful to put the regexp for checkboxes in a variable
> somewhere so it doesn't get out of sync. I wasn't sure though, so I went
> with the simpler solution for now.
>
> My FSF copyright assignment should be on file, but let me know if there
> are any issues there.
>


-- 
The Kafka Pandemic

Please learn what misopathy is.
https://thekafkapandemic.blogspot.com/2013/10/why-some-diseases-are-wronged.html



Re: Org table: emphasizing calculated cell

2021-08-27 Thread Samuel Wales
out of curiosity, do common spreadsheets implement the feature of
distinguishing calculated results from entered values?  i find myself
wanting that too, but don't know if that desire is unusual.


On 8/27/21, Nick Dokos  wrote:
> Jarmo Hurri  writes:
>
>> Greetings Norwid.
>>
>> Norwid Behrnd  writes:
>>
>>> try extending the format of the table formula with asterisks, i.e.
>>>
>>> ```
>>> | quantity |  value |
>>> |--+|
>>> | A|  1 |
>>> | B|  3 |
>>> |--+|
>>> | *C*  | *0.33* |
>>>
>>> #+TBLFM:  @4$2=@-2/@-1; *%.2f*
>>> ```
>>>
>>> Subsequently, issue the call ```C-c *``` for an update while the
>>> cursor is within the table.  This approach works well enough for me
>>> (equally for emphasis with enclosing forward slashes, or underscores)
>>> in Emacs' native display (backed by elpa-org 9.4.0) as well as for a
>>> subsequent export into .html and display (e.g., in Firefox), or .tex.
>>
>> Excellent, this is a working solution for the basic case. Much
>> appreciated!
>>
>> This solution seems to change the contents of a cell, not only its
>> formatting. So the following, where I try to increase the value of "C"
>> by one, leads to an error:
>>
>> ```
>> | quantity | value  |
>> |--+|
>> | A| 1  |
>> | B| 3  |
>> |--+|
>> | *C*  | *0.33* |
>> | D| #ERROR |
>>
>> #+TBLFM: @4$2=@-2/@-1; *%.2f*::@5$2=@-1+1
>> ```
>>
>> I wonder if there is a way around this effect?
>>
>
> The error here is that `*0.33*' is no longer a string that can be converted
> to a number,
> so the calculator barfs.
>
> TUrn on formula debugging with `C-c {' and try evaluating it.
>
> --
> Nick
>
> "There are only two hard problems in computer science: cache
> invalidation, naming things, and off-by-one errors." -Martin Fowler
>
>
>


-- 
The Kafka Pandemic

Please learn what misopathy is.
https://thekafkapandemic.blogspot.com/2013/10/why-some-diseases-are-wronged.html



Re: recording the refile commands

2021-08-18 Thread Samuel Wales
apropos log and refile: org-log-refile

On 8/18/21, Jean-Daniel  wrote:
> Hello,
>
> There are many problems that can be represented by a tree, and the org mode
> refile UI is actually a good UI to refactor a tree of headings. My idea is
> to transform my hierarchical data into an org-mode file, and use the refile
> UI to apply changes to the tree. If the refile actions are recorded, then I
> can process externally this record of tree changes and get them reviewed
> and later applied.
>
> Do you see a good way to record a "refile session"?
> Maybe I can just turn some logging before the refile session and parse the
> log?
>
> One example of such a tree I need to refactor is a set of directories and
> markdown files making up a wiki.
>
> Regards,
>


-- 
The Kafka Pandemic

Please learn what misopathy is.
https://thekafkapandemic.blogspot.com/2013/10/why-some-diseases-are-wronged.html



Re: Org + git branches for derived files

2021-08-13 Thread Samuel Wales
it is an interesting question as many things go into the product:

- org file
- your .el files
- org version
- emacs version
- os
- hw
- export commands run

so the desire to keep the product is understandable.  not only is it
effort to find the export commands run, but other stuff might change
out from under you.

could you perhaps export to something more compressible like ascii or
latex only?  and then use whatever org uses to create pdf?  git isn't
supposed to be for recreatable products, but ... is it TRULY trivially
recreatable?  :)

a colophon in the result can be useful maybe.


On 8/13/21, Rob Sargent  wrote:
>
>
>> On Aug 13, 2021, at 7:53 PM, Rob Sargent  wrote:
>>
>>
>>
>>> On Aug 13, 2021, at 6:54 PM, Mark Barton  wrote:
>>>
>>> Ken,
>>>
>>> You could consider using git-lfs, Large File Support. There is some setup
>>> and then you can say track *.pdf and that will tell git to track the
>>> binary file in a more efficient way. I use this mailing for csv files
>>> that I want to have a snapshot version of with the Jupyter notebook that
>>> used them. Once you are tracking the files with git-lfs, they will be
>>> tracked with the normal git commits.
>>>
>>> I agree that the best practice is not to commit these types of files, but
>>> sometimes it is handy to. By committing the PDF files to the repo, I can
>>> use Working Copy, a git client, on my iPad to quickly reference a
>>> document. Since the iPad cannot run Emacs, I am unable to regenerate the
>>> PDF from there.
>>>
>>> Mark
>>
>> If you’re using GitHub or gitlab you can place artifacts along side your
>> code repo. One often sees executables and jars there. Typically built and
>> updated by mechanisms on the holster on a  “release” action or similar
>> event
>
> I see autocorrect preferred “holster” to “hoster”
>
>
>
>


-- 
The Kafka Pandemic

Please learn what misopathy is.
https://thekafkapandemic.blogspot.com/2013/10/why-some-diseases-are-wronged.html



Re: archiving speed [was Re: Tips on maintaining history in Org Mode]

2021-08-11 Thread Samuel Wales
what is the current status of hierarchy in archive files?  surely they
don't deal with updating categories and updating hierarchy structure
[sounds brittle and syncy]?  i'm thinking it isn't hierarchical at
present, except when you have a doneified task with children?


On 8/11/21, Tim Cross  wrote:
> I think the problem with just using append to file is that it won't
> preserve the shape of the file. For example, if I had a file with
>
> * Notes
> ** Note 1
>blah blah
> ** Note 2 blah blah
>
> * Tasks
> ** DONE task 1
> ** TODO Task 2
>
> and I decide to archive note 1 and task 1, I would like them to both appear
> under the same headings and with the same level. If the process just uses
> append to file, I can have this for the first archiving i.e.
>
> * Noes
> ** Note 1
>
> * Tasks
> ** DONE task 1
>
> but then later, I decide to archive note 2, if append file is used, I will
> end up with
>
> * Notes
> ** Note 1
>
> * Taks
> ** DONE task 1
>
> * Notes
> ** Note 2
>
> which is not what I want. I want
>
> * Notes
> ** Note 1
> ** Note 2
>
> * Tasks
> ** DONE Task 1
>
> So, if we want to preserve hierarchies in our archive files and not have
> everything jumbled up together, the system has to parse the file. If you
> are also using something like Categories, then even more work needs to be
> odne to update the category lists.
>
> What I tend to do is mark items with the ARCHIVE tag and leave them in the
> file and then every few months, move archived data to archive files.  It
> can still get slow, but I don't do it often, so it isn't too much of a
> hassle.
>
>
> On Thu, 12 Aug 2021 at 08:23, Samuel Wales  wrote:
>
>> thanks for the clarification.  are you saying that, for every archived
>> entry, it calculates teh category property, using the original org
>> file, in order to add a category property to just one archived entry?
>>
>> that would certainly slow down more and more, but it sends me back to
>> my question about whether append to file would work.
>> i.e. build the single entry in a temporary buffer then write that
>> region to a file on disk.
>>
>> On 8/10/21, Ihor Radchenko  wrote:
>> > Samuel Wales  writes:
>> >
>> >> i should clarify.  bulk archiving slows down even with /nonexistent/
>> >> (have not tried empty) archives.  as part of normal and expected
>> >> operation, bulk creates the archive for the first entry, and then
>> >> subsequent entries are added.  those get slower and slower.
>> >
>> > That's what I suspected. I also see this and my suggestion helped
>> > archiving speed in my case.
>> >
>> >> i use (olpath category itags).  i will try (file time) when i can, if
>> >> that still applies.  my brain needs to be more operational.
>> >
>> > When you use category, every time you modify the original file (not the
>> > archive!), Org mode re-calculates *all* the categories in the original
>> > Org file. It happens for every single archived heading. If your
>> > original
>> > Org file is large, re-calculations make things extremely slow.
>> >
>> > Best,
>> > Ihor
>> >
>>
>>
>> --
>> The Kafka Pandemic
>>
>> Please learn what misopathy is.
>>
>> https://thekafkapandemic.blogspot.com/2013/10/why-some-diseases-are-wronged.html
>>
>>
>
> --
> regards,
>
> Tim
>
> --
> Tim Cross
>


-- 
The Kafka Pandemic

Please learn what misopathy is.
https://thekafkapandemic.blogspot.com/2013/10/why-some-diseases-are-wronged.html



Re: archiving speed [was Re: Tips on maintaining history in Org Mode]

2021-08-11 Thread Samuel Wales
thank you.

i will give up on archiving categories if needed to make archiving be
practical.  will ahfe to try it as soon as i can.

On 8/11/21, Ihor Radchenko  wrote:
> Samuel Wales  writes:
>
>> thanks for the clarification.  are you saying that, for every archived
>> entry, it calculates teh category property, using the original org
>> file, in order to add a category property to just one archived entry?
>
> Nope. It does not just calculate category for the archived entry, but
> re-calculates all the category properties in the original Org file
> (updating category cache).
>
>> that would certainly slow down more and more, but it sends me back to
>> my question about whether append to file would work.
>> i.e. build the single entry in a temporary buffer then write that
>> region to a file on disk.
>
> Appending can indeed work if your archive location is at the end of the
> file. However, it is not necessary the performance bottleneck. Certainly
> not when the archive file is small.
>
> Best,
> Ihor
>


-- 
The Kafka Pandemic

Please learn what misopathy is.
https://thekafkapandemic.blogspot.com/2013/10/why-some-diseases-are-wronged.html



Re: archiving speed [was Re: Tips on maintaining history in Org Mode]

2021-08-11 Thread Samuel Wales
thanks for the clarification.  are you saying that, for every archived
entry, it calculates teh category property, using the original org
file, in order to add a category property to just one archived entry?

that would certainly slow down more and more, but it sends me back to
my question about whether append to file would work.
i.e. build the single entry in a temporary buffer then write that
region to a file on disk.

On 8/10/21, Ihor Radchenko  wrote:
> Samuel Wales  writes:
>
>> i should clarify.  bulk archiving slows down even with /nonexistent/
>> (have not tried empty) archives.  as part of normal and expected
>> operation, bulk creates the archive for the first entry, and then
>> subsequent entries are added.  those get slower and slower.
>
> That's what I suspected. I also see this and my suggestion helped
> archiving speed in my case.
>
>> i use (olpath category itags).  i will try (file time) when i can, if
>> that still applies.  my brain needs to be more operational.
>
> When you use category, every time you modify the original file (not the
> archive!), Org mode re-calculates *all* the categories in the original
> Org file. It happens for every single archived heading. If your original
> Org file is large, re-calculations make things extremely slow.
>
> Best,
> Ihor
>


-- 
The Kafka Pandemic

Please learn what misopathy is.
https://thekafkapandemic.blogspot.com/2013/10/why-some-diseases-are-wronged.html



Re: archiving speed [was Re: Tips on maintaining history in Org Mode]

2021-08-10 Thread Samuel Wales
i should clarify.  bulk archiving slows down even with /nonexistent/
(have not tried empty) archives.  as part of normal and expected
operation, bulk creates the archive for the first entry, and then
subsequent entries are added.  those get slower and slower.

i was trying to imply e.g. doing archives by year won't fix it.  only
a few entries are enough to slow it down.

i use (olpath category itags).  i will try (file time) when i can, if
that still applies.  my brain needs to be more operational.

i should mention that i did also find a bug, but was not able to
narrow it down.  it has been a while, but it was something like not
killing the original entry for one of the entries.  i was unable to
figure out what conditions needed to obtain for this to occur.


On 8/10/21, Ihor Radchenko  wrote:
> Samuel Wales  writes:
>
>> [this is the case even with zero-size archive files; after a few
>> entries it slows down.]
>
> Do you get the same behaviour with the following code?
>
> (setq org-archive-save-context-info '(file time))
>
> Best,
> Ihor
>


-- 
The Kafka Pandemic

Please learn what misopathy is.
https://thekafkapandemic.blogspot.com/2013/10/why-some-diseases-are-wronged.html



Re: archiving speed [was Re: Tips on maintaining history in Org Mode]

2021-08-10 Thread Samuel Wales
i have not bulk archived in a year or two, because it is too slow for
me.  i am curious why, when appending to an archive file,
append-to-file or write-region are not used, to merely put the entries
there instead of loading the archive file into emacs?

[this is the case even with zero-size archive files; after a few
entries it slows down.]


On 2/28/21, Samuel Wales  wrote:
> thank you for your detaild reply.
>
> more below.
>
> On 2/28/21, Ihor Radchenko  wrote:
>> details why). So, many org commands tend to lag on large archives.
>
> that makes sense.  but why would appending to an archive as the result
> of bulk archiving lag?  if the problem is large archive files, which
> i'd bet is the case for a lot of users and not just me, then could org
> in principle be changed so that all it does is append?  thus not lag?
> like, build the entry in a temporary buffer?
>
> as i see it, having more than one archive file per org file is good
> for speed, but doesn't work in existing org, because iirc e.g. v A in
> the agenda goes org agenda file -> corresponding archive file and will
> miss the archive files that do not have a corresponding org file with
> exactly the same basename sans extension.
>
> i'd be ok with released org either allowing hte user to make
> year-based archives by having all of org recognize them, or my just
> append thing above.  maybe i am missing something.
>
>> The lags can be solved in several ways:
>> 1. Reduce the archive file size
>
> this implies to me e.g. year-based archives, which would fail the v A
> test iiuc.  thus needed extra code.
>
>> 2. Use optimised folding mechanism [1] (this will speed up org-mode in
>> general as well)
>
> i look forward to this filtering down to maint.  :]  [i used to follow
> master but too much for me now for health reasons.]
>
>> 3. (untested) Put #+STARTUP: showeverything at the beginning of the
>>archives, so that nothing is going to be folded
>
> good idea.  my included-by-agenda archive files do seem to be in
> showeveryting mode already for some reason.  but perhaps not when bulk
> archiving.
>
> would it be a silly idea for an fr that org make this an option for
> bulk archiving?  hmm or for archive files in general?
>
>>> i will keep in mind disabling font lock in archive files.  any
>>> suggested code for that?
>>
>> Note that it will mostly affect find-file performance. To disable
>
> if so, then i figure it's a one-time thing per file so no big deal.
> but thanks for hte font lock stuff i didnt' know about.
>
>> Sorry, the config is actually not yet formatted for public use. You can
>> search for the code block containing "defun
>> org-archive--compute-location".
>
> firefox find does not seem to find it.
>
>>
>> You will need that code block and the following code block.
>>
>> [1] https://github.com/yantar92/org
>>
>> Best,
>> Ihor
>>
>>
>
>
> --
> The Kafka Pandemic
>
> Please learn what misopathy is.
> https://thekafkapandemic.blogspot.com/2013/10/why-some-diseases-are-wronged.html
>


-- 
The Kafka Pandemic

Please learn what misopathy is.
https://thekafkapandemic.blogspot.com/2013/10/why-some-diseases-are-wronged.html



Re: Deleting (not archiving) TODO items when done

2021-08-04 Thread Samuel Wales
as peter said, and you can probably collapse and kill the line or kill
using an agenda command.

the archive is used variously.  so is git.  so are items like

  * LOG [ts] header

and also there is logbook.  so where does one store e.g. records of
conversations?  something i struggle with.  in op's case, git and
things like rsnapshot would be the places he could find what he
deleted.

i tend to be conservative, and sometimes doneify and archive AND use
LOG.  drawbacks include impossibly slow archiving [i suspect direct OS
appending to file would be a workaround] and finding needles in
haystacks filled with trivial and near-duplicate entries.

some don't search archives much, some want only meaningful things
there.  etc.  i am learning the maening of bloat.


On 8/4/21, Peter Neilson  wrote:
> On Wed, 04 Aug 2021 13:47:11 -0400, William Denton  wrote:
>
>> When I've marked a TODO item as DONE and want to get it out of my
>> projects list, I've always used C-c C-x C-a
>> (org-archive-subtree-default) to get it out of the way.
>>
>> Today I had to go through the archive file to find an old note about
>> something, and the file was huge because it was filled with many trivial
>>
>> TODOs that didn't need to be archived.  For example, If I'm waiting to
>> hear back from someone, when they reply I usually just want to mark the
>> task DONE and delete it.  I don't need to record it forever.
>>
>> Maybe I've been using the archiving not as intended, but I don't see any
>>
>> other command for getting rid of a TODO.  I can't find a command to
>> delete the current task.  Am I missing something?  Is there a keystroke
>> to delete a TODO?  Or does everyone archive everything?
>>
>> Bill
>>
>> --
>> William Denton
>> https://www.miskatonic.org/
>> Librarian, artist and licensed private investigator.
>> Toronto, Canada
>
> It's just text. Delete it. ^k^k or (for bigger items) establish a region
> and kill it (^w).
>
> If you would like (since you're in emacs) you can write yourself a special
>
> button to do it.
>
>


-- 
The Kafka Pandemic

Please learn what misopathy is.
https://thekafkapandemic.blogspot.com/2013/10/why-some-diseases-are-wronged.html



Re: org-agenda-do-date-earlier does not work on today

2021-07-22 Thread Samuel Wales
my description of the problem is misleading.  if you are in the
previously scheduled section, and move to today by shift right (this
requires a variable setting possibly), then moving to yesterday
toggles moving to today and moving to yesterday.

what i expected was, moving increasingly into the past, by one day,
per invocation of the command.

On 7/22/21, Samuel Wales  wrote:
> i used to be able to do org-agenda-do-date-earlier (shift left) to put
> an item that is scheduled for today into the previously scheduled
> tasks.  however, that is a no-op, at least recently, in recent maint.
>
> has anything changed?
>
> --
> The Kafka Pandemic
>
> Please learn what misopathy is.
> https://thekafkapandemic.blogspot.com/2013/10/why-some-diseases-are-wronged.html
>


-- 
The Kafka Pandemic

Please learn what misopathy is.
https://thekafkapandemic.blogspot.com/2013/10/why-some-diseases-are-wronged.html



org-agenda-do-date-earlier does not work on today

2021-07-22 Thread Samuel Wales
i used to be able to do org-agenda-do-date-earlier (shift left) to put
an item that is scheduled for today into the previously scheduled
tasks.  however, that is a no-op, at least recently, in recent maint.

has anything changed?

-- 
The Kafka Pandemic

Please learn what misopathy is.
https://thekafkapandemic.blogspot.com/2013/10/why-some-diseases-are-wronged.html



Re: Comments break up a paragraph when writing one-setence-per-line

2021-07-16 Thread Samuel Wales
on the other hand, if it were fixed, it would possibly make par sep
blank lines be more controllable in such exporters as ascii.


On 7/16/21, Kaushal Modi  wrote:
> Hello,
>
>
> On Fri, Jul 16, 2021 at 12:35 PM Bruce D'Arcus  wrote:
>
>> On Fri, Jul 16, 2021 at 12:07 PM William Denton  wrote:
>>
>> > However, I was a bit surprised when I found that a commented line
>> > starts
>> a new
>> > paragraph.
>>
>> I hadn't yet discovered that, but I think it should be considered a
>> bug.
>
>
> Comments causing paragraph breaks has been a long known behavior. I learned
> about it few years back, probably from one of the threads here or by
> reading the code.
>
>
>> The output of your example should remove the commented line
>> entirely, and so be:
>>
>> In this paragraph I introduce an idea.
>> But I am sure about this. And here is my conclusion.
>>
>> Perhaps it can be easily fixed?
>>
>
> I don't think it would be a very easy fix as the behavior stems from an
> intentional low level implementation in org-element.el. Changing this
> behavior will cause a regression in all Org exporters out there.
>


-- 
The Kafka Pandemic

Please learn what misopathy is.
https://thekafkapandemic.blogspot.com/2013/10/why-some-diseases-are-wronged.html



Re: A requires/provides approach to linking source code blocks

2021-07-13 Thread Samuel Wales
one thing about org that i think has been making it complex, in
addition to number of features, is non-orthogonality.

On 7/13/21, Tim Cross  wrote:
>
> Tom Gillespie  writes:
>
> [snip]
>
>>
>> Once I wrap up the formal grammar for org, one of the next things I
>> plan to work on is a clear specification for org babel. This is
>> critical because so many of the suggestions that come in deal with
>> individuals' specific problems and thus fail to account for how such
>> features interact with existing features and how the newly proposed
>> feature would block some other features in the future, confuse users,
>> etc. Such suggestions also often fail to account for increased
>> complexity, nor have they been exposed to a sufficient number of
>> examples to reveal fundamental ambiguities in how they could be
>> interpreted. The issues with variable behavior between ob langs for
>> :pre :post :prologue :epilogue etc. are already enough to keep us busy
>> for quite some time.
>>
>
> Yes, that clearly summs up my concerns as well. Often, a 'fix' for some
> problem can seem straight-forward, possibly even trivial, when
> considered only within one person's use case/workflow. Part of what
> makes org so powerful is the level of flexibility it supports. However,
> this flexibility makes it extremely difficult to consider, or even know
> about, all the existing use cases.
>
> I suspect that once we have some formal specifications for babel, the
> next step will be to develop some good unit tests to verify these
> specifications. This would at least highlight/alert developers to
> unforeseen impact from changes and alert them to things they may
> not have considered.
>
>> With regard to this thread in particular, it is of some interest, but
>> there are fundamental issues, including the fact that certain
>> languages (e.g. racket) expect module code to exist somewhere on the
>> file system. There are ways around many of these issues, in fact there
>> are likely many ways around any individual issue, so org babel needs
>> to systematically consider the issues and provide a clear
>> specification, or at least a guide for how such cases should be
>> handled.
>>
>> To give an example from one of my continual pain points: I start
>> writing python or racket in an org src block and then I want it to be
>> a library so that it can be reused by other code both inside and
>> outside the org file without having to resort to noweb.
>>
>
> This is an interesting point. I think a number of languages have
> challenges here. I run into very similar issues with Clojure.
>
> To some extent, I think this is a grey area within the literate
> programming paradigm. The original literate programming model was
> developed at a time when most languages were compiled rather then
> interpreted. You generated source code, compiled it and then ran it.
>
> These days, many 'modern' languages are based around an interpreter and
> concepts like 'just in time' compilation. In org mode, things become
> even more complex because in addition to generation (tangling) of code,
> we also want to have evaluation of code blocks, plus we have added the
> concept of 'sessions'.
>
>> What is the best way to handle this? I don't know. Right now I tangle
>> things and resort to awful hacks for the reuse-in-this-org-file case, but
>> I'm guessing there is a better generic solution which would allow _any_
>> org block to be exported as a library instead of nowebbed in.
>>
>> Before jumping for any particular suggestion for how to handle this
>> we need to explore the diversity of cases that various ob langs
>> present, so that we can find a solution that will work for all of
>> them. After all, packaging code to a library for reuse is an
>> extremely common pattern that org babel should be able to
>> abstract, but it is a major undertaking, not just the addition of a
>> keyword here and there.
>>
>
> Agree. I'm not convinced we really understand the requirements here and
> more exploration and specification is required. The more we add 'simple'
> extensions, options, keywords etc the more likely it is we will make
> this a much harder process and will likely result in even larger
> 'breakage' once we do define a clearer specification.
>
>> In short I suggest that we issue a general moratorium on new org babel
>> feature suggestions until we can stabilize what we already have and
>> provide a clear specification for correct behavior. Until we have that
>> spec
>> we could encourage users to create extensions that implement those
>> features.
>>
>
> Yes. While it might sound harsh or overly limiting, I do think such a
> moratorium may be required. We may be able to lift it once we have some
> core specifications in place. We would still accept bug fixes (though we
> may need to provide some clarity on what is a bug fix and what is a
> feature enhancement/change - I regularly see posts flagged as bug fixes
> which are actually feature enhancements or extensions).

Re: org-ctrl-c-minus includes bullet in links

2021-07-09 Thread Samuel Wales
yes, in recent maint.  thanks for testing.

On 7/9/21, Mark Barton  wrote:
>
>
>> On Jul 9, 2021, at 6:12 PM, Samuel Wales  wrote:
>>
>> this might be a bad bug report.  it seems intermittent.
>>
>> recent maint.
>>
>> create headers each with a link on it.  mark all.  org-ctrl-c-minus.
>>
>> this has incorrectly put - as part of the link descriptions.
>>
>> --
>> The Kafka Pandemic
>>
>> Please learn what misopathy is.
>> https://thekafkapandemic.blogspot.com/2013/10/why-some-diseases-are-wronged.html
>>
>
>
> I realize you said it was intermittent, but is this example below what you
> are describing except that it worked in my case?
>
> ** TODO test org-ctrl-c-minus
> [2021-07-09 Fri 18:49]
> *** [[x-devonthink-item://27605B38-B418-4B49-A086-DFEFBAAD5FC5][Ragged point
> inn_2021-07-02]]
> ***
> [[x-devonthink-item://%3c8d99415d-20fc-4e2d-b41b-9cc43d97b...@gmail.com%3E][Re:
> First Aid Class]]
>
> I then highlighted the two headings with links and used org-ctrl-c-minus to
> get:
>
> ** TODO test org-ctrl-c-minus
> [2021-07-09 Fri 18:49]
> - [[x-devonthink-item://27605B38-B418-4B49-A086-DFEFBAAD5FC5][Ragged point
> inn_2021-07-02]]
> -
> [[x-devonthink-item://%3c8d99415d-20fc-4e2d-b41b-9cc43d97b...@gmail.com%3E][Re:
> First Aid Class]]
>
> I compiled from the master branch yesterday.
> "GNU Emacs 28.0.50 (build 1, x86_64-apple-darwin20.5.0, NS appkit-2022.50
> Version 11.4 (Build 20F71))
>  of 2021-07-08"
>
>


-- 
The Kafka Pandemic

Please learn what misopathy is.
https://thekafkapandemic.blogspot.com/2013/10/why-some-diseases-are-wronged.html



org-ctrl-c-minus includes bullet in links

2021-07-09 Thread Samuel Wales
this might be a bad bug report.  it seems intermittent.

recent maint.

create headers each with a link on it.  mark all.  org-ctrl-c-minus.

this has incorrectly put - as part of the link descriptions.

-- 
The Kafka Pandemic

Please learn what misopathy is.
https://thekafkapandemic.blogspot.com/2013/10/why-some-diseases-are-wronged.html



Re: org-agenda-move-date-from-past-immediately-to-today could work for non-days

2021-07-05 Thread Samuel Wales
i am referring to this code in org-agenda-date-later.  i do not
understand why there is (equal arg 1):

(when (and org-agenda-move-date-from-past-immediately-to-today
   (equal arg 1)
   (or (not what) (eq what 'day))
   (not (save-match-data (org-at-date-range-p
  (setq cdate (org-parse-time-string (match-string 0) 'nodefault)
cdate (calendar-absolute-from-gregorian
   (list (nth 4 cdate) (nth 3 cdate) (nth 5 cdate)))
today (org-today))
  (when (> today cdate)
;; immediately shift to today
(setq arg (- today cdate

i would want to move to today if needed, then the number of days, such
as 7 here:

  (defun alpha-org-agenda-do-date-later--week ()
(interactive)
(org-agenda-do-date-later 7))

but perhaps there is a good reason for restricting this variable to
controlling only a single day move?

On 6/20/21, Samuel Wales  wrote:
> org-agenda-move-date-from-past-immediately-to-today moves a ts
> immediately to today in agenda, but only if you do
> org-agenda-do-date-later by one day.  if you instead do it by 7 days
> or so, it will check and not do the feature.
>
> i keep getting surprised by this, so i thought perhaps newcomers would
> be too.  do you think it makes sense to drop that check and make the
> variable work consistently for all time periods?  imo that would be
> the least surprising and most useful behavior.
>
> the drawbck of not dong so is that you take past scheduled, for
> example, and move them by weeks into the future, only to find out
> later that you moved them into the past.  but perhaps others have
> different sensibilities and there is some reason for the check.
>
> --
> The Kafka Pandemic
>
> Please learn what misopathy is.
> https://thekafkapandemic.blogspot.com/2013/10/why-some-diseases-are-wronged.html
>


-- 
The Kafka Pandemic

Please learn what misopathy is.
https://thekafkapandemic.blogspot.com/2013/10/why-some-diseases-are-wronged.html



Re: Virtually prefix headlines according to content

2021-06-29 Thread Samuel Wales
along similar lines one possibility is to stick a symbol into the
stars.  similar code could also indicate that scheduled and deadline.

On 6/29/21, John Kitchin  wrote:
> you could use this alternative to just change the display without adding
> the tag:
>
> (org-map-entries (lambda ()
>   (looking-at org-heading-regexp)
>   (put-text-property (match-beginning 2) (match-end 2) 'display (concat "GH
> " (match-string 2
>  "+GITHUB={.+}")
>
> There might be some clever way to tie that onto fontlock, or some kind of
> hook to make it also work for entries as you create them.
> John
>
> ---
> Professor John Kitchin (he/him/his)
> Doherty Hall A207F
> Department of Chemical Engineering
> Carnegie Mellon University
> Pittsburgh, PA 15213
> 412-268-7803
> @johnkitchin
> http://kitchingroup.cheme.cmu.edu
>
>
>
> On Tue, Jun 29, 2021 at 9:35 AM Juan Manuel Macías 
> wrote:
>
>> Rodrigo Morales writes:
>>
>> > What I would like to know is whether it is possible to format a
>> > headline
>> > by taking into consideration the properties it has. For example, in
>> > this
>> > specific scenario, I would like to make all headlines that have a
>> > "GITHUB" to show "GH" before the actual headline (the content would
>> > look
>> > like this).
>>
>> You can define a function with `org-map-entries' that adds (for example)
>> a
>> tag :github: to all headers with the property GITHUB:
>>
>> #+begin_src emacs-lisp
>>   (defun add-github-tag ()
>> (interactive)
>> (org-map-entries (lambda ()
>>(save-restriction
>>  (save-excursion
>>(org-narrow-to-subtree)
>>(goto-char (point-min))
>>(end-of-line)
>>(insert "  :github:"
>>  "+GITHUB={.+}"))
>>
>> (add-hook 'org-mode-hook #'add-github-tag)
>> #+end_src
>>
>> Best regards,
>>
>> Juan Manuel
>>
>>
>>
>


-- 
The Kafka Pandemic

Please learn what misopathy is.
https://thekafkapandemic.blogspot.com/2013/10/why-some-diseases-are-wronged.html



org-agenda-move-date-from-past-immediately-to-today could work for non-days

2021-06-20 Thread Samuel Wales
org-agenda-move-date-from-past-immediately-to-today moves a ts
immediately to today in agenda, but only if you do
org-agenda-do-date-later by one day.  if you instead do it by 7 days
or so, it will check and not do the feature.

i keep getting surprised by this, so i thought perhaps newcomers would
be too.  do you think it makes sense to drop that check and make the
variable work consistently for all time periods?  imo that would be
the least surprising and most useful behavior.

the drawbck of not dong so is that you take past scheduled, for
example, and move them by weeks into the future, only to find out
later that you moved them into the past.  but perhaps others have
different sensibilities and there is some reason for the check.

-- 
The Kafka Pandemic

Please learn what misopathy is.
https://thekafkapandemic.blogspot.com/2013/10/why-some-diseases-are-wronged.html



Re: literate programming, development log -- ideas? (ominbus reply)

2021-06-10 Thread Samuel Wales
undo [or equivalent] in buffer.  no saving to disk.

emacs auto save to an auto-expiring directory

emacs backups every save to an auto-expiring directory

git snapshots when i feel like it.  search as needed.

branching in the text itself, by use of comments above if it is
incoming/new and below if it is old/reference.

many use git branch but i wouldn't remember the branch was in git and
i don't want to have to rely on git for such things unless it disrupts
the text without it.  for me it is merely an archive.  it is not an
active repository of future possibilities and current ongoing
activities.  even with magit, git ui is complex to me. its storage
model is not merely an endofuctor of dags.

so i use only basic features when possible.  many years later i still
fear merges/rebases and even stashes and find the merge/rebase
presentation to be quite bizarre and can't believe anybody finds it
the most useful.  certain sequences of staging, unstaging, and
snaphotting can actually cause buffer corruption.  git notes feature
is another complexity which while small i'd rather have git recognize
all file permissions by default.

incidentally, rsync wrapper called rsnapshot works well.  i wouldn't
use it for branching.  you can use unix commands = win.


On 6/9/21, Dr. Arne Babenhauserheide  wrote:
>
> Eric S Fraga  writes:
>
>>> Not sure if it counts as off-topic for this thread, but does everyone
>>> use Git to manage their Org docs and notes?
>>
>> I use a variety of version control systems but for multiple computers I
>> use unison to keep them all synchronised.
>
> I use Mercurial for all my private versiontracking.
>
> Best wishes,
> Arne
> --
> Unpolitisch sein
> heißt politisch sein
> ohne es zu merken
>


-- 
The Kafka Pandemic

Please learn what misopathy is.
https://thekafkapandemic.blogspot.com/2013/10/why-some-diseases-are-wronged.html



Re: Cannot schedule something for 2039?

2021-06-07 Thread Samuel Wales
fwiw i ran this once:

  ;;(/ (org-time-string-to-seconds "--01-01 00:00") 60.0) 4222846500.0
  ;;(/ (org-time-string-to-seconds "-0001-12-31 00:00") 60.0) -1035068671.7
  ;;  oops
  ;;(/ (org-time-string-to-seconds "-12-31 00:00") 60.0)  -1035594271.7
  ;;(/ (org-time-string-to-seconds "0001-12-31 00:00") 60.0)  -1035068671.7
  ;;(/ (org-time-string-to-seconds "1000-12-31 00:00") 60.0) -509645791.7
  ;;(/ (org-time-string-to-seconds "1776-12-31 00:00") 60.0) -101508031.7
  ;;(/ (org-time-string-to-seconds "1900-12-31 00:00") 60.0) -36291900.0
  ;;   nan on non-64
  ;;(/ (org-time-string-to-seconds "1901-12-31 00:00") 60.0) -35766300.0
  ;;(/ (org-time-string-to-seconds "1934-12-31 00:00") 60.0) -18409980.0
  ;;(/ (org-time-string-to-seconds "1960-12-31 00:00") 60.0) -4734300.0
  ;;(/ (org-time-string-to-seconds "1969-12-31 00:00") 60.0) -1020.0
  ;;(/ (org-time-string-to-seconds "1970-01-01 00:00") 60.0) 420.0
  ;;(/ (org-time-string-to-seconds "1980-01-01 00:00") 60.0) 5259300.0
  ;;(/ (org-time-string-to-seconds "1990-01-01 00:00") 60.0) 10519620.0
  ;;(/ (org-time-string-to-seconds "2000-01-01 00:00") 60.0) 15778500.0
  ;;(/ (org-time-string-to-seconds "2010-01-01 00:00") 60.0) 21038820.0
  ;;(/ (org-time-string-to-seconds "2038-01-01 00:00") 60.0) 35765700.0
  ;;(/ (org-time-string-to-seconds "2138-01-01 00:00") 60.0) 88360260.0
  ;;(/ (org-time-string-to-seconds "-01-01 00:00") 60.0) 4222846500.0
  ;;   nan on non-64


On 6/7/21, Alan Schmitt  wrote:
> Hello Richard,
>
> On 2021-06-07 11:17, Richard Lawrence 
> writes:
>
>> whoa, that's a weird behavior, but it seems not to be a bug. I learned
>> something today!
>>
>> It looks like some Emacs implementations don't support dates after
>> 2038-1-1, so Org doesn't let you specify them by default. See the
>> variable `org-read-date-force-compatible-dates'. I think you want to set
>> this variable to nil.
>
> Thanks a lot for pointing to this variable, its docstring is quite
> interesting.
>
> I’m trying the workaround suggested (using a diary sexp, i.e.,
> "<%%(diary-date 2039 4 2)>" in my case), but I cannot test it (the
> agenda for that date won’t build, at the date is outside the range). I
> guess this will be fixed by then ;)
>
> Best,
>
> Alan
>


-- 
The Kafka Pandemic

Please learn what misopathy is.
https://thekafkapandemic.blogspot.com/2013/10/why-some-diseases-are-wronged.html



Re: source blocks mangled when edited

2021-05-30 Thread Samuel Wales
idk if this will help as you probably know all of it already.  butg
you asked for any help so here goes.  i run maint, not master or any
emacs versions.  weird that you are missing 3 cols?

===

here are notes on my workaround which wfm in the meantime if you are
willing to do the same thing.  i was having trouble getting exported
indentation for example blocks.

;; fix default for source and example block indentation
;;
;; when you edit a source or data block, org will by default
;; remove some leading whitespace and then add 2 spaces, so the
;; whole block in org is indented by 2.
;;
;; (the deleted rectangle seems to be the maximum amount of
;; whitespace common to all lines in each block.)
;;
;; initial tabs get converted to spaces.  example blocks get
;; unindented during export incorrectly.  mistakes are possible.
;; this as non-nil prevents all that.  see led for more.
;;
;; we EITHER unindent all and set this non-nil, OR put up with
;; stripping of leading whitespace from blocks where we don't
;; want the indentation stripped.
;;
;; /i prefer t./ it is not possible in babel to indent without
;; having the special feature of removing the whitespace
;; rectangle.
;;
;; you can use -i to locally do t.  there isn't an arg that
;; locally does the reverse of -i.  i.e. to do nil.
;;
;; i have gotten comfortable with no indentation and imo it is a good
default for newcomers and does not surprise.
;;
;; source blocks might actually work without indentation even
;; with the default value, but then when you edit it indents.
(setq org-src-preserve-indentation t)
;; (setq org-src-preserve-indentation nil)
;;
;; only has effect if org-src-preserve-indentation is nil
;; (setq org-edit-src-content-indentation 0)


On 5/30/21, Michael Gauland  wrote:
> I've stared having trouble editing source blocks.    When I use C-c ' to
> edit block, the editing behaves as expected, but when I C-c ' to return
> to the main org file, the code is altered in strange ways.  I've had
> trouble coming up with a really small example, but the attached file
> seems to consistently demonstrate the problem, even when running emacs
> without my settings.
>
> The file has two identical source blocks. The first generally behaves
> fine, though some lines get extra indentation.
>
> The second suffers more serious distortions. For example, the first line
> changes from "digraph G {" to "aph G {".
>
> I've seen this with other types of code as well (at least SQL and json),
> so it's not specific to dot.
>
> I'm running emacs 26.1 on Debian 10.9, with org build from git.
>
> I'm not even sure how to start tracking this down. Any help would be
> greatly appreciated!
>
> Kind regards,
>
> Mike Gauland
>
>


-- 
The Kafka Pandemic

Please learn what misopathy is.
https://thekafkapandemic.blogspot.com/2013/10/why-some-diseases-are-wronged.html



Re: Custom <> possibility?

2021-05-21 Thread Samuel Wales
tahnk you.  that makes sense for validity.  still not sure about
uniqueness.  it's not needed for me to understand, though.
of course with across-export link stability then uniqueness would be meaningful.


On 5/21/21, Nicolas Goaziou  wrote:
> Hello,
>
> Samuel Wales  writes:
>
>> so i am curious what the purpose of the default is?
>
> I think the purpose of the default value is to offer a solution that
> works for everyone. It is certainly not the best one in all situations.
>
> For example, I heard that even in 2021, using full Unicode in a URL is
> not good idea. Yet, some users may want to use Unicode symbols in
> a target.
>
> Regards,
> --
> Nicolas Goaziou
>


-- 
The Kafka Pandemic

Please learn what misopathy is.
https://thekafkapandemic.blogspot.com/2013/10/why-some-diseases-are-wronged.html



Re: Custom <> possibility?

2021-05-20 Thread Samuel Wales
thanks for the example.  yes, that is the example i was thinkng of.

i was asking, why does adding uniqueness do any good currently.  if
the user has your example as follows, it does create duplicates in the
output, but i don't get why that all by itself needs fixing by
default.

===vvv
I may try to give the example here:

<>
Lorem ipsum dolor sit amet, consectetur adipiscing elit. Donec a diam
lectus. Sed sit amet ipsum mauris.

<>
Vivamus fermentum semper porta. Nunc diam velit, adipiscing ut
tristique vitae, sagittis vel odio. Maecenas convallis ullamcorper
ultricies.

which results in:


Lorem ipsum dolor sit amet, consectetur adipiscing elit. Donec a diam
lectus. Sed sit amet ipsum mauris.




Vivamus fermentum semper porta. Nunc diam velit, adipiscing ut
tristique vitae, sagittis vel odio. Maecenas convallis ullamcorper
ultricies.

===^^^

so the duplicates in the output there are apparently a problem.  i am
not sure why, unless a link needs to point to each.  perhaps so that
the reader of the web page can point to each?  but as you say,
generating the document again foils that plot.

[note: i started the thread about toc links.  this is a subtly
different question although it overlaps.]


On 5/20/21, Jean Louis  wrote:
> * Samuel Wales  [2021-05-21 01:19]:
>> thanks for pointing us to this variable.
>>
>> docstring says "This process ensures that these values are unique and
>> valid...", so it sounds like you could create non-unique or invalid
>> identifiers without it.
>>
>> does this mean, for example, if the user exports a subtree with two
>> link targets with the same user label, then if this variable is
>> non-nil, then the output could include more than one link target?
>
> I may try to give the example here:
>
> <>
> Lorem ipsum dolor sit amet, consectetur adipiscing elit. Donec a diam
> lectus. Sed sit amet ipsum mauris.
>
> <>
> Vivamus fermentum semper porta. Nunc diam velit, adipiscing ut
> tristique vitae, sagittis vel odio. Maecenas convallis ullamcorper
> ultricies.
>
> which results in:
>
> 
> Lorem ipsum dolor sit amet, consectetur adipiscing elit. Donec a diam
> lectus. Sed sit amet ipsum mauris.
> 
>
> 
> 
> Vivamus fermentum semper porta. Nunc diam velit, adipiscing ut
> tristique vitae, sagittis vel odio. Maecenas convallis ullamcorper
> ultricies.
> 
>
>> what if this var were nil [the default], my brain is not working well
>> now, but it seems as if the exporter could still get confused which
>> target to link to, even if it is not printing duplicatedly-named
>> targets.
>>
>> so i am curious what the purpose of the default is?
>
> You already discovered the purpose: "This process ensures that these
> values are unique and valid..."
>
> Randomly generated internal hyperlinks are not part of author's
> document creation and I don't believe they can be unique across all
> documents as they rely on randomity, not uniqueness, but they may be
> unique in one document. The sentence should say "This process ensures
> that these values are unique to specific document and valid"
>
> Problem with it is that those random anchors/links are random, and
> that makes it a bad default for user. A user may bookmark the link
>
> https://www.example.com/doc#org2cf8625 with some title, but with the
> next document generation same link may appear as
> https://www.example.com/doc#org6ac9de0 and that means that bookmark
> disappeared, at least for HTML export.
>
> For me personally I am editing Org text (not files) on a meta level
> where all objects have its unique ID and from there I can create Org
> files. Then each object of a structure of meta level Org has its
> unique ID. Also the document has its unique ID. Then it becomes
> possible to automatically create anchors like <<1:17311:31121>> which
> are truly unique across all documents, remain immutable, and are
> trackable. With "trackable" I mean that it is possible to generate a
> list of "referenced by" documents, documents which hyperlink to that
> anchor.
>
> --
> Jean
>
> Take action in Free Software Foundation campaigns:
> https://www.fsf.org/campaigns
>
> Sign an open letter in support of Richard M. Stallman
> https://stallmansupport.org/
> https://rms-support-letter.github.io/
>
>


-- 
The Kafka Pandemic

Please learn what misopathy is.
https://thekafkapandemic.blogspot.com/2013/10/why-some-diseases-are-wronged.html



Re: Custom <> possibility?

2021-05-20 Thread Samuel Wales
thanks for pointing us to this variable.

docstring says "This process ensures that these values are unique and
valid...", so it sounds like you could create non-unique or invalid
identifiers without it.

does this mean, for example, if the user exports a subtree with two
link targets with the same user label, then if this variable is
non-nil, then the output could include more than one link target?

what if this var were nil [the default], my brain is not working well
now, but it seems as if the exporter could still get confused which
target to link to, even if it is not printing duplicatedly-named
targets.

so i am curious what the purpose of the default is?

On 5/20/21, Jean Louis  wrote:
> * Nicolas Goaziou  [2021-05-20 23:00]:
>> > Is there a possibility to tell Org, that <> really remains
>> > "target" as in id="target" instead of a random ID?
>>
>> See `org-html-prefer-user-labels'.
>
> Thanks.
>
>
> --
> Jean
>
> Take action in Free Software Foundation campaigns:
> https://www.fsf.org/campaigns
>
> Sign an open letter in support of Richard M. Stallman
> https://stallmansupport.org/
> https://rms-support-letter.github.io/
>
>
>


-- 
The Kafka Pandemic

Please learn what misopathy is.
https://thekafkapandemic.blogspot.com/2013/10/why-some-diseases-are-wronged.html



Re: [IMPORTANT] The contrib/ directory now lives outside of Org's repository

2021-05-15 Thread Samuel Wales
thanks.

On 5/15/21, Bastien  wrote:
> Samuel Wales  writes:
>
>> i just noticed that htmlize is not htere.  i think it used to be.  a
>> quick search shows no obvious place where it resides.
>
> See https://code.orgmode.org/bzg/org-mode/commit/d0ced9894
>
> --
>  Bastien
>


-- 
The Kafka Pandemic

Please learn what misopathy is.
https://thekafkapandemic.blogspot.com/2013/10/why-some-diseases-are-wronged.html



Re: [PATCH] org-refile.el: Add org-refile-reverse which toggles org-reverse-note-order

2021-05-15 Thread Samuel Wales
sounds good to decouple those, but i interpret org-refile-reverse to
mean "refile in reverse".  from a to b -> from b to a.  fwiw.  thus,
you could be on a and goto b and then do a reverse refile.  that would
be a useful operation.  so i suggest org-refile-reverse-order or so.

On 5/15/21, Bastien  wrote:
> Hi Adam,
>
> Adam Spiers  writes:
>
>> This is useful for prepending to the start of the target headline
>> instead of appending to the end, or vice-versa depending on
>> org-reverse-note-order.
>
> Applied in master as 9e127a720, thanks.
>
> --
>  Bastien
>
>


-- 
The Kafka Pandemic

Please learn what misopathy is.
https://thekafkapandemic.blogspot.com/2013/10/why-some-diseases-are-wronged.html



Re: [IMPORTANT] The contrib/ directory now lives outside of Org's repository

2021-05-15 Thread Samuel Wales
great.  thank you.

i just noticed that htmlize is not htere.  i think it used to be.  a
quick search shows no obvious place where it resides.

On 5/15/21, Bastien  wrote:
> Bastien  writes:
>
>> The files previously stored in the contrib/ directory of Org's repo
>> now lives here: https://git.sr.ht/~bzg/org-contrib
>
> You can now install org-contrib as a new NonGNU ELPA package:
> https://elpa.nongnu.org/nongnu/
>
> --
>  Bastien
>
>


-- 
The Kafka Pandemic

Please learn what misopathy is.
https://thekafkapandemic.blogspot.com/2013/10/why-some-diseases-are-wronged.html



Re: [bug] archiving creates duplicate entries

2021-05-09 Thread Samuel Wales
i have confirmed that this bug occurs as follows.

archiving commands append to a buffer for the archive.  they do not
save, revert, or kill that buffer.  my shell workaround, to allow
archiving given completely unusably slow archiving, moved the archive
files [so that they would not be slow].

therefore there were no archives on disk.  but a full buffer.

therefore, archiving appended to existing buffers that did not match
what was on disk.  then saved.  ergo duplicates.

suggested fix: kill the archive buffer before appending to it, if it
is marked as unmodified.

if it is not marked as unmodified, maybe it is ok to append?  idk.


On 5/9/21, Samuel Wales  wrote:
> when i do a bulk archive, it will sometimes put 2 copies
> entries into the archive file.  it is more likely to occur
> if i am archiving more tasks.  at times, it seems certain
> entries do this repeatably, but i am not sure.
>
> there are times when i think i have reset everything (git is
> clean, archives are moved out of teh way) but this still
> occurs.  i cannot make an mwe but it seemed worth reporting.
> where is it getting the duplicates from?  idk.  it has to be
> either the source .org file or the newly created and written
> archive file.  idk if there are any caches or text
> properties or some hidden stuff in the agenda.  but i can
> tell you that there have been times when i experimented with
> not cleaning everything and the duplicates increased.  each
> run would create a new duplicate of certain entries.
>
> btw i have been trying to archive tasks to files for a year
> now.  it is too slow for me.  so i hit on the idea of moving
> archives out of the way, then archiving a little at a time
> to new archive files, then using the shell to append the new
> archived entries to the old archive files, then moving the
> old archive files back.  thus, this isn't an issue of big
> archive files.
>
> wish i could provide more for you or even figure out
> debugging but i cannot; just hope it will ring bells.
>


-- 
The Kafka Pandemic

Please learn what misopathy is.
https://thekafkapandemic.blogspot.com/2013/10/why-some-diseases-are-wronged.html



[bug] archiving creates duplicate entries

2021-05-09 Thread Samuel Wales
when i do a bulk archive, it will sometimes put 2 copies
entries into the archive file.  it is more likely to occur
if i am archiving more tasks.  at times, it seems certain
entries do this repeatably, but i am not sure.

there are times when i think i have reset everything (git is
clean, archives are moved out of teh way) but this still
occurs.  i cannot make an mwe but it seemed worth reporting.
where is it getting the duplicates from?  idk.  it has to be
either the source .org file or the newly created and written
archive file.  idk if there are any caches or text
properties or some hidden stuff in the agenda.  but i can
tell you that there have been times when i experimented with
not cleaning everything and the duplicates increased.  each
run would create a new duplicate of certain entries.

btw i have been trying to archive tasks to files for a year
now.  it is too slow for me.  so i hit on the idea of moving
archives out of the way, then archiving a little at a time
to new archive files, then using the shell to append the new
archived entries to the old archive files, then moving the
old archive files back.  thus, this isn't an issue of big
archive files.

wish i could provide more for you or even figure out
debugging but i cannot; just hope it will ring bells.



  1   2   3   4   5   6   7   8   9   10   >