I found that Exuberant Ctags gives no output message on most empty files, except for *.ml files.
To reproduce, try following commands:
$ touch empty.txt empty.c empty.ml
$ ctags empty.txt
$ ctags empty.c
$ ctags empty.ml
ctags: Unexpected end of file: empty.ml
How can I make ctags behave consistently on all file types?
macOS Mojave 10.14.2
Exuberant Ctags 5.8
The bug was fixed in Universal-ctags (https://ctags.io) .
Related
When I open emacs I am getting this warning
external/slc6_amd64_gcc630/lib/libtiff.so.5: no version information available (required by emacs)
I recently changed my system from sl6 to centos7. So, it is a result of this. How do I resolve this issue?
Just a guess, but I think you could get away with a symlink from your libtiff to the location expected by your emacs binary (assuming you don't just want to recompile / get an emacs binary for your distro).
Make a link to your libtiff wherever it may be,
find /usr/lib -name libtiff.so.5 2>/dev/null
or locate libtiff.so.5
from that expected by the emacs binary,
ldd /usr/bin/emacs | awk '/libtiff/ { print $3 }'
replacing the /usr/lib/, /usr/bin/emacs with your actual locations.
I'm trying to use Eclipse for Parallel Application Developers to do some MPI stuff but I can't get the program to compile. Below is the error I'm getting in the console:
Description Resource Path Location Type
/bin/sh: mpic++: command not found prog C/C++ Problem
I use mpic++ from the command line (bash shell) to successfully compile programs. When I run the command using bourne shell I get an error.
/bin/sh mpic++
/usr/local/bin/mpic++: /usr/local/bin/mpic++: cannot execute binary file
When I use sudo I still get the same error. But when I first change to the bourne shell then run the mpic++ command it works.
/bin/sh
sh-3.2$ mpic++
clang: error: no input files
I've been looking at ways to change the shell used by eclipse so I can use the bash shell because I can call mpic++ without any problems. I've also tried launching eclipse with sudo but that didn't work.
I have compiled mpi in eclipse successfully. Please follow the steps:
In terminal type:
$ which mpicxx
/usr/local/bin/mpicxx
You should get the mpicxx binary path as result. I have my mpicxx in /usr/local/bin/ directory.
In eclipse, go to project properties:
Set GCC C Compiler as: /usr/local/bin/mpicxx
Also set GCC C+ Compiler as: /usr/local/bin/mpicxx
Set MacOS X C++ Linker as: /usr/local/bin/mpicxx. Also set All options as -L/usr/local/lib
After im use command projectile-regenerate-tags and I get:
Ctags excuberant don't be a command
I'm very new at this so I'll give as many details as possible:
Using Mac OSX 10.7.4
Installed today:
TextMate 1.5.11
RVM 1.15.5 by Wayne Seguin
GCC 10.7
Ruby 1.9.3
Rails 3.2.8
Haml 3.1.7
Sass 3.2.1
Haml instructions:
To run Haml from the command line, just use
haml input.haml output.html
When I input the above command, my Terminal responds:
Errno::ENOENT: No such file or directory - input.haml
Use --trace for backtrace.
When I input:
--trace
It returns:
-bash: --trace: command not found
Having similar issue with Sass:
$ sass --watch style.scss:style.css
>>> Sass is watching for changes. Press Ctrl-C to stop.
Errno::ENOENT: No such file or directory - style.scss
Use --trace for backtrace.
Do I need to create the input.haml and output.haml files first and put them in a directory somewhere? If so, can someone give me a very specific path where the folder needs to go?
Similar question for the Sass files -- do they need to be in a particular folder for the Terminal to locate them?
And.. unsure why --trace is not working...
Can someone advise me on how to troubleshoot this? I am only familiar with HTML/CSS, and have been asked to learn Haml/Sass by my team.
input.haml should exist and should be a haml file. output.html is where the output will be stored (and will be overwritten if it exists)
Those files can be anywhere you want, but if they aren't in the current directory you'll need to adjust the path accordingly.
Similarly for sass style.scss must exist and the resulting CSS will be output to style.css
You're not using --trace command properly. In UNIX command line, programs that run in command line (also called cli as in command line interface) use options known as flags that begin with - or --. So without ever having used HAML code, I see that this is a flag used like this:
➜ ~ uname -a
Darwin Angel.local 12.0.0 Darwin Kernel Version 12.0.0: Sun Jun 24 23:00:16 PDT 2012; root:xnu-2050.7.9~1/RELEASE_X86_64 x86_64
➜ ~ cat > test.haml
#content
.left.column
%h2 Welcome to our site!
%p= print_information
.right.column
= render :partial => "sidebar"
^C
➜ ~ haml test.haml
Exception on line 4: undefined local variable or method `print_information' for #<Object:0x007f9844896cd0>
Use --trace for backtrace.
Use --trace for backtrace.
➜ ~ haml test.haml --trace
test.haml:4:in `block in render': undefined local variable or method `print_information' for #<Object:0x007fd83b9f8650> (NameError)
from /Users/atma/.rvm/gems/ruby-1.9.3-p194/gems/haml-3.1.7/lib/haml/engine.rb:191:in `eval'
from /Users/atma/.rvm/gems/ruby-1.9.3-p194/gems/haml-3.1.7/lib/haml/engine.rb:191:in `render'
from /Users/atma/.rvm/gems/ruby-1.9.3-p194/gems/haml-3.1.7/lib/haml/exec.rb:281:in `process_result'
from /Users/atma/.rvm/gems/ruby-1.9.3-p194/gems/haml-3.1.7/lib/haml/exec.rb:41:in `parse'
from /Users/atma/.rvm/gems/ruby-1.9.3-p194/gems/haml-3.1.7/lib/haml/exec.rb:21:in `parse!'
from /Users/atma/.rvm/gems/ruby-1.9.3-p194/gems/haml-3.1.7/bin/haml:9:in `<top (required)>'
from /Users/atma/.rvm/gems/ruby-1.9.3-p194/bin/haml:19:in `load'
from /Users/atma/.rvm/gems/ruby-1.9.3-p194/bin/haml:19:in `<main>'
from /Users/atma/.rvm/gems/ruby-1.9.3-p194/bin/ruby_noexec_wrapper:14:in `eval'
from /Users/atma/.rvm/gems/ruby-1.9.3-p194/bin/ruby_noexec_wrapper:14:in `<main>'
➜ ~
Apart from that, I just installed haml gem on MacOSX 10.8 via RVM and works fine. Running ruby filename.haml might come with a helpful message also.
Using Google Chat screenshare, my online co-workers looked at my Terminal activity and then gave me some commands to use so that the file(s) could be found. Next, they had me put a simple line of "Hello World" in my input.haml document for testing purposes.
Today haml can now find the file(s), and when I gave it the command regarding the input.haml and output.html files, it successfully transferred the data from input to output.
So the problem was my lack of knowledge regarding how to get to the correct directory in Terminal.
Doras-MacBook-Pro:~ whisperland$ cd/Users/whisperland/documents/ haml input.haml
-bash: cd/Users/whisperland/documents/: No such file or directory
Doras-MacBook-Pro:~ whisperland$ cd documents
Doras-MacBook-Pro:documents whisperland$ ls
document.haml output.html
input.haml typography.rtf
Doras-MacBook-Pro:documents whisperland$ haml input.haml
hello world
Doras-MacBook-Pro:documents whisperland$ haml input.haml output.html
My project requires dependency of libxml2 am using autotools to check the dependencies & install the same. I declare the dependency of using the following macro in configure.ac
echo -n "checking if libxml2 is present... "
PKG_CHECK_MODULES([LIBXML2], [libxml-2.0 >= 2.6.19],
[echo "yes (features requiring libxml2 enabled)" AC_DEFINE(HAVE_LIB_XML, 1, [define if libxml2 is present])],
[echo "no"] )
The macro works as desired in GNU/Linux.
But somehow it fails in Solaris with the following error
checking if libxml2 is present... ./configure: line 11586: syntax error near unexpected token `LIBXML2,'
./configure: line 11586: `PKG_CHECK_MODULES(LIBXML2, libxml-2.0 >= 2.6.19,'
Googled for a solution, most of them complain of pkg-config not being installed. But in my test machine its actually installed, checked it by executing the following command.
bash-3.00# pkg-config libxml-2.0 --modversion
2.6.23
Some suggestions would be welcomed.
The PKG_CHECK_MODULES macro doesn't seem to be expanded properly. When you installed pkg-config, did it install pkg.m4 (in somewhere like /usr/share/aclocal)? If so, try running aclocal again (maybe with -I m4, if you've got custom m4 code in the m4 subdirectory) and then run autoconf.
If that doesn't work and pkg.m4 was installed, try running autoreconf -f (and maybe autoreconf -i -f).
If that doesn't work, you'll need to copy pkg.m4 to a directory for your package. Usually this is the m4 subdirectory. Set ACLOCAL_AMFLAGS = -I m4 (or ACLOCAL_AMFLAGS = -I m4 --install) in Makefile.am (if you're using automake), and AC_CONFIG_MACRO_DIR([m4]) in configure.ac. Then run aclocal -I m4 and autoconf and ./configure.