search

emacs-helm / helm-org

53 stars 9 forks source link

‘org-element-at-point’ cannot be used in non-Org buffer #29

Open tkossak opened 2 days ago

tkossak commented 2 days ago

Reposting https://github.com/syl20bnr/spacemacs/issues/16575 since it seems to be an issue with helm-org.

When I press SPC j i (command spacemacs/helm-jump-in-buffer) I get multiple errors: ⛔ Warning (org-element): ‘org-element-at-point’ cannot be used in non-Org buffer #<buffer *helm org inbuffer*> (helm-major-mode)

Reproduction

  1. Install spacemacs from scratch 
    
mv ~/.emacs.d ~/.emacs.d.old
mv ~/.spacemacs ~/.spacemacs.old

git clone --recursive https://github.com/syl20bnr/spacemacs ~/.emacs.d

2. Create [dotfile](https://gist.github.com/tkossak/76833f64c27c2aff52a4bbbdd0799717) as `~/.spacemacs`. Only few lines changed from default dotfile - I added org layer, removed multi cursor layer and added these 2 lines:
(setq helm-org-format-outline-path nil)
(setq org-startup-indented 't)
```
  1. Create sample org file eg test.org with content: 
    * heading1
blabla
  2. Start spacemacs and perform first time installation of all packages it asks for
  3. Open test.org and press SPC j i. Result: image
fnussbaum commented 1 day ago

FWIW in Spacemacs SPC j i in an Org buffer calls helm-org-in-buffer-headings. The warnings seems to come from helm-org-indent-headings-1 enabling org-indent-mode in the Helm buffer.

thierryvolpiatto commented 1 day ago

Kossak @.***> writes:

  1. ( ) text/plain (*) text/html

Reposting syl20bnr/spacemacs#16575 since it seems to be an issue with helm-org.

When I press SPC j i (command spacemacs/helm-jump-in-buffer) I get multiple errors: ⛔ Warning (org-element): ‘org-element-at-point’ cannot be used in non-Org buffer #<buffer helm org inbuffer> (helm-major-mode)

Sorry I am not aware of the spacemacs* commands.

Reproduction

  1. Install spacemacs from scratch

I do not use Spacemacs (and will not install it).

Please use a minimal config starting from emacs -Q or use the script emacs-helm.sh to reproduce your bug. If your packages are installed from package.el, you can also use the isolate package action from M-x helm-packages.

Thanks.

-- Thierry