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

markdown-edit-code-block errors with (void-function nil) #284

Closed
blaenk opened this issue Nov 14, 2017 · 3 comments
Closed

markdown-edit-code-block errors with (void-function nil) #284

blaenk opened this issue Nov 14, 2017 · 3 comments
Labels

Comments

@blaenk
Copy link

blaenk commented Nov 14, 2017

Expected Behavior

For an edit-indirect buffer to open with the contents of the codeblock.

Actual Behavior

The following backtrace.

Steps to Reproduce

Buffer like this with cursor in the middle of the codeblock:

``` ini
[/Script/EngineSettings.GameMapsSettings]
+GameModeMapPrefixes=(Name="DM",GameMode="/Script/UnrealTournament.UTDMGameMode")
+GameModeClassAliases=(Name="DM",GameMode="/Script/UnrealTournament.UTDMGameMode")
```

This only seems to happen for languages that don't have obvious mappings between codeblock language marker and emacs mode, so I wonder if it's related to the changes made for #251 , something about this comment #251 (comment) or the one after it. Sorry it's been a while since I wrote that.

Backtrace

Debugger entered--Lisp error: (void-function nil)
  nil()
  #f(compiled-function (parent-buffer beg end) #<bytecode>)(#<buffer asdf> 11 218)
  edit-indirect--create-indirect-buffer(11 218 #<overlay from 11 to 218 in asdf>)
  edit-indirect--get-edit-indirect-buffer(11 218)
  edit-indirect-region(11 218 display-buffer)
  markdown-edit-code-block()
  funcall-interactively(markdown-edit-code-block)
  call-interactively(markdown-edit-code-block nil nil)
  command-execute(markdown-edit-code-block)

Software Versions

  • Markdown Mode: 2.4-dev
  • Emacs: 26.0.50
  • OS: archlinux 4.13.12-1-ARCH
@blaenk
Copy link
Author

blaenk commented Nov 14, 2017

Please see 3b92618#commitcomment-25598489 , I think it may be the cause of this issue.

@jrblevin
Copy link
Owner

Thanks for following up on this aspect. I forgot to address in from previous comments, but I think it is fixed now.

@jrblevin jrblevin added the bug label Nov 14, 2017
@blaenk
Copy link
Author

blaenk commented Nov 14, 2017

It appears to be working 👍

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

No branches or pull requests

2 participants