-
Notifications
You must be signed in to change notification settings - Fork 10
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
Not able to pipe into eless #18
Comments
Hello, Using the same
So based on the
messages you get, it looks like the macOS grep does not support It's failing for each of these 3 grep checks! IMO I am using the old (2009) GNU grep 2.6.3 that came with RHEL 6.6.. Can you get GNU grep on your machine too?
We can tackle this later once the |
@mobyte0 Can you try installing GNU grep using these instructions (looks like someone else using the mac-default |
I have successfully installed GNU grep on Homebrew and I'm on version 3.1. I would recommend listing the needed version of grep in the requirements. While I'm not getting the grep errors anymore, the empty GUI emacs opens again.
|
Thanks for the followup.
Of course, I will do that now. You are probably the first macOS user without GNU grep who tried this.. that's all :)
Alright.. so let's debug this.. Let me think more about it and get back to you. |
Yeah, the base is BSD grep 2.5.1, so perhaps this could effect many BSD users? |
Looks like we have a different variant of Compare the
vs yours:
So one thing is obvious.. the But looks like, on your system, it literally created Let me google the right way to do this on mac OS. |
@mobyte0 What is your
|
Does this work on your system?
|
@mobyte0 Do you want to update to the latest |
Alright, it's working. I pulled your new commit and by using GNU coreutils in place of the stock BSD utils (I followed the guidance here: https://apple.stackexchange.com/a/69332. However, people using shells other than bash may need to configure their paths in the way the shell requires), the pipe echo into eless is now working. Thank you so much for your help! |
|
|
Hmm.. haven't used |
Well, technically, as long as eless is put somewhere in your standard search path (whether it's a symlink or whatnot), all is good. I just decided to put it in my home search path as a symlink, so maybe I'm just overthinking it. |
Great! I'll anyways update Requirements to mention that Thanks for sticking through the debug. |
However, when using Also, thanks for your quick help, I'm glad this could be resolved in a short amount of time. |
Yes, please.. with the Can you also try setting |
If adaptation is a goal, I would not require GNU grep and would use an alternate approach. There are alternatives (untested 😄):
Can be:
Or instead of using Perl regexes (
It's likely already installed and I'm pretty sure it's installed by default more than GNU grep. Also if you use
some_var=${some_var/bash_builtins/builtins} |
Interesting. Can you elaborate? |
Continuing this here: #19
We use a lot of 3rd party vendor tools that are tested to work well with env setup for tcsh.. and legacy. |
OS: MacOS 10.12.6
Shell: fish 2.5.0/bash 4.4.0(1)-release
A GUI emacs opens without anything in it.
The text was updated successfully, but these errors were encountered: