Recently after un update of emacs-notmuch I get this error
Unrecognized option: --deduplicate=address
command: notmuch address --format\=sexp --format-version\=2 --output\=recipients --deduplicate\=address from\:enrico.pirani\#gmail.com\ or\ from\:enrico.pirani\#pec.it
exit status: 1
stderr:
Unrecognized option: --deduplicate=address
whenever I try to search for an address in my bddb. I use notmuch version 0.20.2 with emacs 24.5.1 on OSX 10.9
The notmuch-emacs interface is intimately tied with the notmuch command-line interface, and they will need to have compatible versions, preferrably the same. You're using a newer version of the notmuch-emacs interface than the cli.
M-x notmuch-hello-versions RET in emacs will show you the versions.
Typically, you'd see this after installing notmuch-emacs from MELPA, and notmuch cli from the package manager.
Related
After installing code-oss on Manjaro Linux along with the Jupyter extension for code and jupyter-notebooks itself, the extension seems to error when I try to do anything Jupyter related inside code. If I try to create a new notebook from the command pallete, it pops up a dialog saying this:
Command 'Jupyter: Create New Jupyter Notebook' resulted in an error (command 'jupyter.createnewnotebook' not found)
Code then tells me that the extension activation failed and to open the chrome developer console for more information. This is what the chrome console then says:
extension activation failed Error: Extension 'ms-toolsai.jupyter' CANNOT use API proposal: notebookEditor. Its package.json#enabledApiProposals-property declares: but NOT notebookEditor. The missing proposal MUST be added and you must start in extension development mode or use the following command line switch: --enable-proposed-api ms-toolsai.jupyter
Initial Pop-up error
Chrome Console error
You can solve that problem by inserting"enable-proposed-api": ["ms-toolsai.jupyter"] in the start settings of vs code. So press CTRL+ALT+P -> "Preference: Configure Runtime Arguments" then insert the upper line. After that restart vscode.
Had the same problem and found out this is happening because of the open source version of code - OSS. It does not have the proper config in the product.json.
The accepted solution to add to Runtime Arguments unfortunately didn't work on Arch.
Easiest solution for me was to install code-features from AUR.
You can find more info on arch wiki site
Or directly on microsoft docs regarding oss code issues.
The solution to add "enable-proposed-api": ["ms-toolsai.jupyter"] to the runtime of vscode didn't work for me on Arch linux. But when I started vscode from the command line using the argument "--enable-proposed-api ms-toolsai.jupyter" the problem was solved. So I created a custom desktop launcher for this:
Fist, copy the desktop launcher to your applications folder
$ cp /usr/share/applications/code-oss.desktop ~/.local/share/applications/.
Then edit the new file:
$ nano ~/.local/share/applications/code-oss.desktop
Now add "--enable-proposed-api ms-toolsai.jupyter" to both of the Exec lines like so:
[Desktop Entry]
Name=Code - OSS
Comment=Code Editing. Redefined.
GenericName=Text Editor
Exec=/usr/bin/code-oss --enable-proposed-api ms-toolsai.jupyter --unity-launch %F
Icon=com.visualstudio.code.oss
Type=Application
StartupNotify=false
StartupWMClass=Code
Categories=TextEditor;Development;IDE;
MimeType=text/plain;application/x-code-oss-workspace;
Actions=new-empty-window;
Keywords=vscode;
[Desktop Action new-empty-window]
Name=New Empty Window
Exec=/usr/bin/code-oss --enable-proposed-api ms-toolsai.jupyter --new-window %F
Icon=com.visualstudio.code.oss
I restarted my computer and the problem was solved.
When I try to run code in emacs swift-mode with C-c C-z, I receive the following message:
'warning: unable to find and load segment named '__OBJC_RO' at
0x7fff6e030000 in '/usr/lib/libobjc.A.dylib' in macosx dynamic loader
plug-in.
warning: unable to find and load segment named '__OBJC_RW' at
0x7fff919d9080 in '/usr/lib/libobjc.A.dylib' in macosx dynamic loader
plug-in.'
I am running emacs version 26.3 and macOS version 10.15
Does anybody have a resolution for this issue?
When I build perl use microsoft vc2017, I got an error :
Running pm_to_blib for cpan/Module-Load-Conditional directly
Running pm_to_blib for cpan/Module-Loaded directly
Running pm_to_blib for cpan/NEXT directly
Running pm_to_blib for dist/Net-Ping directly
Running pm_to_blib for cpan/Params-Check directly
Running pm_to_blib for cpan/Perl-OSType directly
Running pm_to_blib for cpan/PerlIO-via-QuotedPrint directly
Can't copy p to scripts/p: No such file or directory at Makefile.PL line 26.
Unsuccessful Makefile.PL(cpan/Pod-Checker): code=512 at ..\make_ext.pl line
518.
NMAKE : fatal error U1077: “..\miniperl.exe”: 返回代码 (return code)“0x2”
Stop.
What can I do?
This seems to be a bug in the Windows SDK, see
Perl ticket #133666
VS forum setargv.obj is broken in the latest windows sdk
The Perl bug reporter confirmed that the bug went away after updating the SDK. Another alternative seems to be to switch from a CFG=DebugFull to a CFG=Debug build.
I tried to install the nix package manager on an Android device with termux.
When I try to execute the nix applicatives (for instance nix-store or nix-env) I get the following error
/nix/store/y9mfv3sx75mbfibf1zna1kq9v98fk2nb-nix-1.11.16/bin/nix-env:
error while loading shared libraries:
/nix/store/kfk65xrfzndyyz6if5fxk4wrwz76h2lh-glibc-2.25-49/lib/libc.so:
invalid ELF header
The file seems to be a script for the GNU linker, so I'm wondering what is the problem, could it be that termux's version of ld is unable to correctly interpret GNU Linker's scripts?
Thanks in advance for any help.
Edit: It seems that if unset the LD_PRELOADED and the LD_LIBRARY_PATH variables the nix-applications work fine. Problem is that in doing so termux cannot lunch any other non nix application, such as bash for instance.
My problem is that when I try to start debuggin in DDT in Eclipse (Kepler) an error shows up:
Error in final launch sequence
Failed to execute MI command:
-gdb-set auto-solib-add on
Error message from debugger back end:
No symbol table is loaded.
Use the "file" command.
No symbol table is loaded.
Use the "file" command.
I've compiled the application with -gc and -g flag but it didn't help.
I'm using original DMD compiler.
Sounds like you are working on Windows, DMD has no GDB support there yet. You can either use windbg from the command line or use the Visual Studio plugin, which converts the debug info after compiling.
The issue that I had is that the compiler (DMD) is not working with GDB under Windows. If somebody wants to use DDT with debugging support, he needs to use GDC compiler.
This actually is mentioned in the "Debugging" page:
http://wiki.dlang.org/Debugging