Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Disabling helm-org-rifle-fontify-headings breaks helm-org-rifle-agenda-files #74

Open
darim1 opened this issue Mar 7, 2022 · 6 comments

Comments

@darim1
Copy link

darim1 commented Mar 7, 2022

I tried to disable helm-org-rifle-fontify-headings and encounter errors, when trying to conduct helm-org-rifle-agenda-files:

Error running timer: (error "In ‘org.org<Finanzen>’ source: ‘#[nil \\301�!\\205\0\\302\\303\\304!�\"\\207 [helm-pattern s-present? helm-org-rifle--get-candidates-in-buffer helm-attr buffer] 3]’ 

Re-enabling brings back full functionality. Is there a workaround?

I use emacs 27.2 with latest org-mode/ helm-org-rifle.

@alphapapa
Copy link
Owner

That shouldn't happen. Unfortunately that message doesn't say what the error is. Please enable debug-on-error and try to provide a full backtrace. (Note that Helm's manipulation of the window configuration may interfere with seeing the backtrace, but it's usually possible to get to it anyway, e.g. by changing to the backtrace buffer.)

@darim1
Copy link
Author

darim1 commented Mar 8, 2022

Ok, that is indeed a tricky task... I could not manage to copy the raw text from the buffer. Sorry. Instead I created a screenshot. I hope that is ok, too:

screenshot

@alphapapa
Copy link
Owner

Thanks, that helps.

I think that a change in a newer version of Org has broken something. Please give this information:

  1. Tell me the exact Org version you're using (i.e. use M-x org-version RET).
  2. Do C-h f org-get-outline-path RET and paste the docstring that is shown.
  3. In that Org file that that "Strom [0/3]" heading is found in, put point on that heading, and do M-: (org-get-outline-path t) RET and paste the result.

@darim1
Copy link
Author

darim1 commented Mar 12, 2022

Please find below my ansers:

  1. I am using org-mode 9.5.2
org-get-outline-path is a compiled Lisp function in ‘org.el’.

(org-get-outline-path &optional WITH-SELF USE-CACHE)

Return the outline path to the current entry.

An outline path is a list of ancestors for current headline, as
a list of strings.  Statistics cookies are removed and links are
replaced with their description, if any, or their path otherwise.

When optional argument WITH-SELF is non-nil, the path also
includes the current headline.

When optional argument USE-CACHE is non-nil, cache outline paths
between calls to this function so as to avoid backtracking.  This
argument is useful when planning to find more than one outline
path in the same document.  In that case, there are two
conditions to satisfy:
  - ‘org-outline-path-cache’ is set to nil before starting the
    process;
  - outline paths are computed by increasing buffer positions.

  1. ("Energie" "Strom")

Thanks!

@alphapapa
Copy link
Owner

Thanks.

This seems strange: in the screenshot, the "Strom [0/3]" heading has its statistics cookie present, but in the docstring of that function, it says that the cookies are removed.

I wonder if your config has multiple versions of Org installed and is loading an older one and then a newer version, or something weird like that.

Also, you show the outline path as being ("Energie" "Strom") (which is correct), but in the screenshot it's (("Energie") "Strom [0/3]").

I'd suggest trying to reproduce the problem in a clean Emacs configuration, e.g. using this script: https://github.com/alphapapa/with-emacs.sh

@darim1
Copy link
Author

darim1 commented Mar 17, 2022

Ok. BTW I've tried on different machines with different installations (Windows and Linux) from the same .emacs and ancounter the issue in any environment.

I'd like to follow your suggestion, but cannot elaborate on this. What is the intention/benefit in using clean emacs?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants