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

Option to add custom prefix/postfix to PROMPT #24

Closed
z0rc opened this issue Oct 20, 2016 · 6 comments
Closed

Option to add custom prefix/postfix to PROMPT #24

z0rc opened this issue Oct 20, 2016 · 6 comments

Comments

@z0rc
Copy link

z0rc commented Oct 20, 2016

I'd like to define my own indicators that will be included in PROMPT. I can easily create a function or variable to return indicator string, but I miss is a proper way to inject it into geometry PROMPT.

@frm
Copy link
Member

frm commented Oct 21, 2016

You can change the prompt symbols, if I understood correctly.

Simply export one of these variables in your .zshrc.

You can find an example in my dotfiles. I'm changing the exit value symbol plus a couple of colors.

@z0rc
Copy link
Author

z0rc commented Oct 21, 2016

Not really what I need. I want to expand prompt with my own data. Technically this looks doable with adding my strings to symbols there. But I'd like to see something like https://github.com/nojhan/liquidprompt#adding-a-prefixpostfix

@desyncr
Copy link
Member

desyncr commented Nov 7, 2016

Maybe some kind of callback, ie geometry_(r)prompt_[pre|post]_callback but I think it's too complex to implement to be fully customizable.

@frm
Copy link
Member

frm commented Nov 7, 2016

It seems a bit complex, yeah. I think I'll let this hang on the bottom of the list since there are more pressing issues and features.

@desyncr
Copy link
Member

desyncr commented Dec 9, 2016

@z0rc Now geometry has support for plugins (#43, #45 ), which means you can add your custom prompts into geometry. Here is a working example.

@desyncr
Copy link
Member

desyncr commented Dec 9, 2016

I'm closing this as it should be solved.

@desyncr desyncr closed this as completed Dec 9, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants