I recently installed Spacemacs on Windows. The "smart search" command SPC / does not work. When I press SPC / I get the error:
Wrong type argument: commandp, helm-do-grep
There seem to be some issue that mention this - https://github.com/syl20bnr/spacemacs/issues/8463
Anyone know what's up?
If my understanding is correct, your spacemacs is not finding ag or grep. Spacemacs uses ag, grep, ack, pt for search. If ag is not found it falls back to grep and so on. Grep, ack are *nix commands. You probably have to install cygwin and add it to the path.
But the best way is to install this port of ag for windows and add it to the path. ag for windows
This isn't a solution, but it is a workaround that I ended up using. I was used to using Spacemacs on Mac. I installed it on windows and encountered the above error. On Windows it was using grep by default for searching, whereas on Mac it was using ag.
I installed ag on Windows that the search is back to working now. I installed ag following the instructions on here. It uses scoop for the installation which is installed via Powershell.
Related
I'm using wslv2 on Windows 10 Pro running on the dev channel. I've made sure it's fully up to date, then completely uninstalled wsl and ubuntu, then reinstalled them.
Despite this, I don't have a working mount option :(
wings#machine:~$ wsl --mount
Unknown command: --mount
If I understand correctly, you are trying to do this from the wsl terminal. But this must be done through powershell.
This is due to the --mount option being not yet released.
The documentation on Microsoft doesn't highlight it very much but you have to use early windows 11 preview to be able to use the mount option.
See here: https://learn.microsoft.com/en-us/windows/wsl/wsl2-mount-disk#prerequisites
From what I understand there, the actual release is scheduled for this month (Sept. 21) in Win 10.
I have installed NetBSD 6.1.5 with full installation setting. However, when I run startx it says no screens could be found. So i tried "X -configure" and then "X -config ~/xconfig.conf.new" and I was brought to a very generic screen with a black x crosshair, but I was unable to exit this using the suggested ctrl+alt+backspace, so I had to force power off and check if my keyboard was recognized in the conf file generated, which it was. I have installed xdm, xterm, Xorg, and other X programs.
I am not familiar with setting up desktop environments from scratch. I am a newb who is used to Ubuntu esque installers doing that stuff for me.
Would someone be able to walk me though the installation or point me to a link which explains a step by step process?
What happens if you rename your xorg.conf.new to /etc/X11/xorg.conf? Does startx or xdm work then?
Are you running this inside a VirtualBox or other emulator?
I have NetBSD on a Thinkpad T420 which I occasionally boot into Windows, and I've setup VirtualBox to be able to run the same NetBSD install when I'm in Windows. The key difference in the xorg.conf file is in the Device section:
Section "Device"
Driver "vesa"
EndSection
Also I've found the free version of http://mobaxterm.mobatek.net/ very handy - I use it to ssh into the virtual NetBSD box and then run X apps and have them display on the Windows desktop.
Final note - you might want to look out for the NetBSD-7 RC1 which should be out 'Real Soon Now', as there are some very handy improvements, including better support for most modern display hardware :)
I found that running startx from any directory with a .xinitrc file gives strange behavior in amd64 6.1.5 and 6.1.4. Delete (or rename) any .xinitrc files and try
xinit /path/to/windowmanager
Please read Chapter 9 of NetBSD Guide:
http://www.netbsd.org/docs/guide/en/chap-x.html
Section 9.9 discusses installing various Desktop Managers/Environments.
It turns out that I could run "X -config xorg.conf.new" as root on host and then ssh using putty to manually launch windows.
I have installed (and re-installed) Octave 3 times on Windows 8, and I still can't get it right. The first and most obvious problem is that the prompt is missing; the screen only shows the flashing underscore that follows the prompt. This is not a major problem since the system properly responds to commands.
The major problem is that Octave crashes whenever it encounters a syntax error, instead of politely giving a diagnostic. This makes for extremely tedious software development.
Is there a way around this problem, or do we just have to wait for one side or the other to come up with an accommodation?
I encountered the same problem. I solved it by this:
create a shortcut to octave.exe, then right click->property-> change the "target" to something like:
C:\Program Files\Octave\Octave3.6.*_gcc*.*.*\bin\octave.exe -i --line-editing
Then it won't exit if u have syntax errors.
I don't understand the meaning of the parameters yet.
reference:
http://exciton.eo.yzu.edu.tw/~lab/?p=1121
Type octave --help can check the meaning of parameters.
-i also --interactvie, to force Octave interactive behavior.
Maybe Octave run at non-interactive mode at default, that means prompt should not be shown and it should terminate immediately when encountered error when reading a file.
I don't know if this will solve your problem, or if this is too bloated of a solution for you, but I use Octave on Windows 7 through Cygwin without any problems.
If you can't get Octave to run on Windows 8, you may consider running Octave through Linux via computer virtualization technology (virtual computer). Two, off the top of my head that you could use are VirtualBox by Oracle or VMWare Player
Once you have it installed, you can go to any number of sites that have pre-built Linux images that you can download and then run inside of Windows 8.X. Do a Google search of for 'Virtualbox images' or as 'VMWare appliances'. You can then download and use that to run the lastest version of Octave. I hope that helps.
Cheers,
Studying vision, I would like to play with the Microsoft Kinect.
Can I use it on my Mac?
I have not found any Library for Mac and fear virtualization on my laptop to use Linux.
I've accessed Kinect data on OSX using openframeworks and the ofxKinect addon (which uses libfreenect and libusb).
It's not the only option, just I've used and worked 'out of the box'.
Try downloading the Zigfu Dev Bundle for mac (http://www.zigfu.com) - that should get you up to speed with kinect development on mac.
Using Kinect on Mac is as easy as ordering Latte.
But there is also a lot of confusion on the Internet and sites that seem to be old and give you the wrong advice such as installing a separate sensor library in addition to OpenNI. Just go to the basic website and download SDK for your MAC:
http://www.openni.org/openni-sdk/
You might need to have prerequsities though I assume you have already installed them, such as:
sudo port install libtool
sudo port install doxygen
restart comp
sudo port install libusb-devel +universal
Troubleshooting:
"sudo rm -f /opt/local/lib/libusb-1.0.0.dylib"
"sudo port clean libusb"
"sudo port install libusb +universal"
No need to compile anything. You should be able to run ./Samples/Bin/SimpleViewer right away after you run sudo ./install.sh.The PROBLEM might be that you have already tried to run it unsuccessfully and put a camera in the wrong state. I have seen errors such as USB intercase cannot be set etc. as a side effect.
Running your code in Eclipse is a different story and may require a few extra steps and changing your Ubuntu code (using openni namespace, different includes, etc.)
I am having problems getting the GTK designer to work with MonoDevelop. I tried 2.4 on Arch Linux and it gave this problem. Then I tried 2.2 on OpenBSD and it gives the exact same problem. Both machines are 64bit.
Instead of having a window to drag things on I just have a blank square:
alt text http://img96.imageshack.us/img96/4766/monodevelop.png
The tutorials I've seen look similar to this though:
alt text http://monodevelop.com/#api/deki/files/142/=Stetic_Tutorial_06.jpg?size=bestfit&width=700&height=425
So what gives? With my blank square I can't drag anything onto it, not a VBox or other container even. It will not react to anything.
Am I missing some sort of GTK# configuration or what? I find it highly improbable that both OSs' packages I tried are broken. Also, I've attached a (huge) bounty to this because this is a pretty big issue for me.
The console output from the starting of Mono and including me trying to drag an element onto the gray box is here
Update
Ok, so I've finally gotten a bit closer to solving the mystery. I use Fluxbox as my window manager usually. Well I tried using both KDE and Gnome-Session and both of them cause MonoDevelop to work properly(though still missing the window border, you could at least drag components onto it). Now my question is what makes Fluxbox not work for it?
I have the same problem in openSUSE 11.3 x64 KDE using Mono JIT compiler version 2.6.7 (tarball Wed Jul 14 18:00:23 UTC 2010) downloaded from here
type -a monodevelop returns:
monodevelop is /usr/bin/monodevelop
monodevelop is /usr/bin/X11/monodevelop
Running monodevelop from terminal gives the following output
1)
WARNING: Cannot find Mozilla directory
containing libgtkembedmoz.so. Some
Addins may not be able to function.
Please set MOZILLA_FIVE_HOME to your
Mozilla directory.
This can be solved by adding an environment variable in your .bashrc file from your home directory.
export MOZILLA_FIVE_HOME='/path/to/libgtkembedmoz.so/directory/'
To find if that library exists on your systems use:
sudo find / -name libgtkembedmoz.so
-print
(from this bug report this library is contain in the Mozilla's XUL Runner package, but in newer versions I don't know if it's still there, I had to use libgtkembedmoz.so provided by Slickedit which was installed in /opt/slickedit/bin/mozilla/)
2)
WARNING [2010-07-29 20:22:37Z]: Inotify watch limit is too low (8192).
To resolve this problem read Inotify Watches Limit
3)
WARNING [2010-07-29 20:22:37Z]: Error creating composed icon gtk-execute___asm0__debug-overlay-22.png__SmallToolbar at size SmallToolbar. Icon __asm0__debug-overlay-22.png__SmallToolbar is 22x22, expected 16x16.
I get the exact same error using Monodevelop 2.4, and I think this could be either from a broken GTK# installation or from a bug in Monodevelop,
Your result is the same as mine, see here. I suggest compiling MonoDevelop from Github and/or using a newer version of gtk-sharp/gdk-sharp
This part
ERROR [2010-07-29 20:22:37Z]: GdkPixbuf-Critical: gdk_pixbuf_composite: assertion `dest_x >= 0 && dest_x + dest_width <= dest->width' failed
appears in GTK and GDK crashes,
If this does not resolve the problem submitting a bug report is the next option. Although this is somehow strange, since I managed to complete the same tutorial using Kubuntu 10.04 LTS 64 bit a few weeks ago.
Uh, that is the designer. If the toolbox didn't show up, go to View->Pads->Toolbox to bring it up.
Note that this Gtk, you can't just drop a button or textbox on the design surface. You have to drop a container control first, and then can place buttons and such inside the container.
set global gtk theme to default
check all bindings depends
try start monodevelop from console and post output on pastebin
"Now my question is what makes Fluxbox not work for it? " remember the GTK protect was made for GNOME project, all the libraries are made to work on that Desktop. so need to see all the dependencies to run it property