Powerline and Fish: How can I remove the large whitespace between the shell prompt and cursor?
I recently started using Arch Linux and just installed Powerline and Fish (version 3.0.0) last week. In my terminal, which is Termite (version 14), there's a large (horizontal) space between the shell prompt and where my cursor is when inputting commands that is quite bothersome.
As additional information, I'm using OMF with the bobthefish theme. When I first installed and used the theme, I didn't notice any change, so I don't know if it's working properly. It does say that it is the active theme though.
It wasn't like this before I installed Powerline. Unfortunately, I haven't been able to find any other discussions on similar problems.
This is how it currently looks in a default-sized terminal:
And in a maximized terminal:
I was thinking that it could be a problem with my font, as I just checked and my font in the termite .config file is Hack at size 9. When I use a Powerline font, however, it doesn't render correctly in the terminal. I tried doing both this way:
font = "Ubuntu Mono derivative Powerline" 11
And this way:
font = Ubuntu Mono derivative Powerline 11
In the terminal config file, but neither display properly. Perhaps the powerline fonts are not in the correct folder. They are located in
~/.local/share/fonts
In fact, other fonts, located in /usr/share/fonts also don't render correctly.
shell fonts arch-linux prompt fish
asked Feb 15 at 4:51
Qhapaq QowiQhapaq Qowi
154
add a comment |
I recently started using Arch Linux and just installed Powerline and Fish (version 3.0.0) last week. In my terminal, which is Termite (version 14), there's a large (horizontal) space between the shell prompt and where my cursor is when inputting commands that is quite bothersome.
As additional information, I'm using OMF with the bobthefish theme. When I first installed and used the theme, I didn't notice any change, so I don't know if it's working properly. It does say that it is the active theme though.
It wasn't like this before I installed Powerline. Unfortunately, I haven't been able to find any other discussions on similar problems.
This is how it currently looks in a default-sized terminal:
And in a maximized terminal:
I was thinking that it could be a problem with my font, as I just checked and my font in the termite .config file is Hack at size 9. When I use a Powerline font, however, it doesn't render correctly in the terminal. I tried doing both this way:
font = "Ubuntu Mono derivative Powerline" 11
And this way:
font = Ubuntu Mono derivative Powerline 11
In the terminal config file, but neither display properly. Perhaps the powerline fonts are not in the correct folder. They are located in
~/.local/share/fonts
In fact, other fonts, located in /usr/share/fonts also don't render correctly.
shell fonts arch-linux prompt fish
asked Feb 15 at 4:51
Qhapaq QowiQhapaq Qowi
154
You should always include the version of all relevant software in your question. In this case fish and termite.
– Kurtis Rader
Feb 15 at 18:43
2
Welcome to Super User! You can freely edit your own posts but for your protection, this must be done under the original user account. It looks like you registered and created a second account, which will also interfere with your ability to comment within your thread and to accept an answer. See Merge my accounts to get your accounts merged, which will solve the problem.
– fixer1234
Feb 15 at 23:30
Just to echo what @fixer1234 says, you can always edit and comment on your own posts. So if you face an issue as you described in an earlier edit of your question, get the accounts merged.
– JakeGould
Feb 16 at 2:12
Hello, I really appreciate the help. I finally was able to get the accounts merged. Apologies for the delay; I've been really swamped with school projects. I was also wondering if superuser was the right place to ask this question or if I should have picked another site. Additionally, I forgot to mention I'm using the theme "bobthefish" I'll update my post.
– Qhapaq Qowi
Feb 22 at 23:56
add a comment |
I recently started using Arch Linux and just installed Powerline and Fish (version 3.0.0) last week. In my terminal, which is Termite (version 14), there's a large (horizontal) space between the shell prompt and where my cursor is when inputting commands that is quite bothersome.
As additional information, I'm using OMF with the bobthefish theme. When I first installed and used the theme, I didn't notice any change, so I don't know if it's working properly. It does say that it is the active theme though.
It wasn't like this before I installed Powerline. Unfortunately, I haven't been able to find any other discussions on similar problems.
This is how it currently looks in a default-sized terminal:
And in a maximized terminal:
I was thinking that it could be a problem with my font, as I just checked and my font in the termite .config file is Hack at size 9. When I use a Powerline font, however, it doesn't render correctly in the terminal. I tried doing both this way:
font = "Ubuntu Mono derivative Powerline" 11
And this way:
font = Ubuntu Mono derivative Powerline 11
In the terminal config file, but neither display properly. Perhaps the powerline fonts are not in the correct folder. They are located in
~/.local/share/fonts
In fact, other fonts, located in /usr/share/fonts also don't render correctly.
shell fonts arch-linux prompt fish
asked Feb 15 at 4:51
Qhapaq QowiQhapaq Qowi
154
I recently started using Arch Linux and just installed Powerline and Fish (version 3.0.0) last week. In my terminal, which is Termite (version 14), there's a large (horizontal) space between the shell prompt and where my cursor is when inputting commands that is quite bothersome.
As additional information, I'm using OMF with the bobthefish theme. When I first installed and used the theme, I didn't notice any change, so I don't know if it's working properly. It does say that it is the active theme though.
It wasn't like this before I installed Powerline. Unfortunately, I haven't been able to find any other discussions on similar problems.
This is how it currently looks in a default-sized terminal:
And in a maximized terminal:
I was thinking that it could be a problem with my font, as I just checked and my font in the termite .config file is Hack at size 9. When I use a Powerline font, however, it doesn't render correctly in the terminal. I tried doing both this way:
font = "Ubuntu Mono derivative Powerline" 11
And this way:
font = Ubuntu Mono derivative Powerline 11
In the terminal config file, but neither display properly. Perhaps the powerline fonts are not in the correct folder. They are located in
~/.local/share/fonts
In fact, other fonts, located in /usr/share/fonts also don't render correctly.
shell fonts arch-linux prompt fish
shell fonts arch-linux prompt fish
asked Feb 15 at 4:51
Qhapaq QowiQhapaq Qowi
154
asked Feb 15 at 4:51
Qhapaq QowiQhapaq Qowi
154
edited Feb 23 at 0:15
Qhapaq Qowi
asked Feb 15 at 4:51
Qhapaq QowiQhapaq Qowi
154
asked Feb 15 at 4:51
Qhapaq QowiQhapaq Qowi
154
asked Feb 15 at 4:51
Qhapaq QowiQhapaq Qowi
154
154
You should always include the version of all relevant software in your question. In this case fish and termite.
– Kurtis Rader
Feb 15 at 18:43
2
Welcome to Super User! You can freely edit your own posts but for your protection, this must be done under the original user account. It looks like you registered and created a second account, which will also interfere with your ability to comment within your thread and to accept an answer. See Merge my accounts to get your accounts merged, which will solve the problem.
– fixer1234
Feb 15 at 23:30
Just to echo what @fixer1234 says, you can always edit and comment on your own posts. So if you face an issue as you described in an earlier edit of your question, get the accounts merged.
– JakeGould
Feb 16 at 2:12
Hello, I really appreciate the help. I finally was able to get the accounts merged. Apologies for the delay; I've been really swamped with school projects. I was also wondering if superuser was the right place to ask this question or if I should have picked another site. Additionally, I forgot to mention I'm using the theme "bobthefish" I'll update my post.
– Qhapaq Qowi
Feb 22 at 23:56
add a comment |
You should always include the version of all relevant software in your question. In this case fish and termite.
– Kurtis Rader
Feb 15 at 18:43
2
Welcome to Super User! You can freely edit your own posts but for your protection, this must be done under the original user account. It looks like you registered and created a second account, which will also interfere with your ability to comment within your thread and to accept an answer. See Merge my accounts to get your accounts merged, which will solve the problem.
– fixer1234
Feb 15 at 23:30
Just to echo what @fixer1234 says, you can always edit and comment on your own posts. So if you face an issue as you described in an earlier edit of your question, get the accounts merged.
– JakeGould
Feb 16 at 2:12
Hello, I really appreciate the help. I finally was able to get the accounts merged. Apologies for the delay; I've been really swamped with school projects. I was also wondering if superuser was the right place to ask this question or if I should have picked another site. Additionally, I forgot to mention I'm using the theme "bobthefish" I'll update my post.
– Qhapaq Qowi
Feb 22 at 23:56
You should always include the version of all relevant software in your question. In this case fish and termite.
– Kurtis Rader
Feb 15 at 18:43
You should always include the version of all relevant software in your question. In this case fish and termite.
– Kurtis Rader
Feb 15 at 18:43
2
2
Welcome to Super User! You can freely edit your own posts but for your protection, this must be done under the original user account. It looks like you registered and created a second account, which will also interfere with your ability to comment within your thread and to accept an answer. See Merge my accounts to get your accounts merged, which will solve the problem.
– fixer1234
Feb 15 at 23:30
Welcome to Super User! You can freely edit your own posts but for your protection, this must be done under the original user account. It looks like you registered and created a second account, which will also interfere with your ability to comment within your thread and to accept an answer. See Merge my accounts to get your accounts merged, which will solve the problem.
– fixer1234
Feb 15 at 23:30
Just to echo what @fixer1234 says, you can always edit and comment on your own posts. So if you face an issue as you described in an earlier edit of your question, get the accounts merged.
– JakeGould
Feb 16 at 2:12
Just to echo what @fixer1234 says, you can always edit and comment on your own posts. So if you face an issue as you described in an earlier edit of your question, get the accounts merged.
– JakeGould
Feb 16 at 2:12
Hello, I really appreciate the help. I finally was able to get the accounts merged. Apologies for the delay; I've been really swamped with school projects. I was also wondering if superuser was the right place to ask this question or if I should have picked another site. Additionally, I forgot to mention I'm using the theme "bobthefish" I'll update my post.
– Qhapaq Qowi
Feb 22 at 23:56
Hello, I really appreciate the help. I finally was able to get the accounts merged. Apologies for the delay; I've been really swamped with school projects. I was also wondering if superuser was the right place to ask this question or if I should have picked another site. Additionally, I forgot to mention I'm using the theme "bobthefish" I'll update my post.
– Qhapaq Qowi
Feb 22 at 23:56
add a comment |
1 Answer
1
active
oldest
votes
This occurs when fish and your terminal don't agree on the width of specific characters.
It is almost always emoji chars since the width of many emoji code points has changed as the Unicode standard has evolved. Complicating matters are magical code points such as U+FE0F which themselves don't have any width but affect the preceding code point.
The simplest solution is to pick different characters. Alternatively, there are various workarounds you can employ to change how fish and your terminal calculate the width of problematic chars.
See, for example, https://github.com/fish-shell/fish-shell/issues/5583
edited Feb 16 at 2:00
JakeGould
32.2k1098141
answered Feb 15 at 18:48
Kurtis RaderKurtis Rader
72947
Thanks for the help! I've looked into it, but have been unable to have any success. I'm a total noob at fish and customizing terminals in general. I'm unable to get anything from using wcwidth or fish_emoji_width. After usingset $fish_emoji_width=2it lists a lot of configuration entires, but when echoingfish_emoji_width, it still only prints a whitespace. Also, most unicode characters are not rendering well and am having difficulty printing them. Any other ideas?
– Qhapaq Qowi
Feb 23 at 0:00
@QhapaqQowi Your syntax for setting a variable is incorrect. It wouldn't even be correct for a POSIX shell like bash. The correct syntax isset fish_emoji_width 2. Note the lack of a dollar or equal sign. Also, if you're having problems with non-ASCII chars in general you should check your locale is correctly set. If you typelocaleyou should see something likeLANG="en_US.UTF-8"; i.e., a UTF-8 locale.
– Kurtis Rader
Feb 24 at 0:00
Wow, well that's embarassing haha. Thank you for the edification! I've been trying to learn more about these things. I updated the locale as you mentioned and it worked!!! Somehow I thought I tried it earlier without success, but I realized that it didn't persist throughout terminal sessions. I've fixed it though, and it behaves properly and persists. Thank you so much; I really appreciate it!
– Qhapaq Qowi
Feb 24 at 4:17
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "3"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f1405951%2fpowerline-and-fish-how-can-i-remove-the-large-whitespace-between-the-shell-prom%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
This occurs when fish and your terminal don't agree on the width of specific characters.
It is almost always emoji chars since the width of many emoji code points has changed as the Unicode standard has evolved. Complicating matters are magical code points such as U+FE0F which themselves don't have any width but affect the preceding code point.
The simplest solution is to pick different characters. Alternatively, there are various workarounds you can employ to change how fish and your terminal calculate the width of problematic chars.
See, for example, https://github.com/fish-shell/fish-shell/issues/5583
edited Feb 16 at 2:00
JakeGould
32.2k1098141
answered Feb 15 at 18:48
Kurtis RaderKurtis Rader
72947
Thanks for the help! I've looked into it, but have been unable to have any success. I'm a total noob at fish and customizing terminals in general. I'm unable to get anything from using wcwidth or fish_emoji_width. After usingset $fish_emoji_width=2it lists a lot of configuration entires, but when echoingfish_emoji_width, it still only prints a whitespace. Also, most unicode characters are not rendering well and am having difficulty printing them. Any other ideas?
– Qhapaq Qowi
Feb 23 at 0:00
@QhapaqQowi Your syntax for setting a variable is incorrect. It wouldn't even be correct for a POSIX shell like bash. The correct syntax isset fish_emoji_width 2. Note the lack of a dollar or equal sign. Also, if you're having problems with non-ASCII chars in general you should check your locale is correctly set. If you typelocaleyou should see something likeLANG="en_US.UTF-8"; i.e., a UTF-8 locale.
– Kurtis Rader
Feb 24 at 0:00
Wow, well that's embarassing haha. Thank you for the edification! I've been trying to learn more about these things. I updated the locale as you mentioned and it worked!!! Somehow I thought I tried it earlier without success, but I realized that it didn't persist throughout terminal sessions. I've fixed it though, and it behaves properly and persists. Thank you so much; I really appreciate it!
– Qhapaq Qowi
Feb 24 at 4:17
add a comment |
This occurs when fish and your terminal don't agree on the width of specific characters.
It is almost always emoji chars since the width of many emoji code points has changed as the Unicode standard has evolved. Complicating matters are magical code points such as U+FE0F which themselves don't have any width but affect the preceding code point.
The simplest solution is to pick different characters. Alternatively, there are various workarounds you can employ to change how fish and your terminal calculate the width of problematic chars.
See, for example, https://github.com/fish-shell/fish-shell/issues/5583
edited Feb 16 at 2:00
JakeGould
32.2k1098141
answered Feb 15 at 18:48
Kurtis RaderKurtis Rader
72947
Thanks for the help! I've looked into it, but have been unable to have any success. I'm a total noob at fish and customizing terminals in general. I'm unable to get anything from using wcwidth or fish_emoji_width. After usingset $fish_emoji_width=2it lists a lot of configuration entires, but when echoingfish_emoji_width, it still only prints a whitespace. Also, most unicode characters are not rendering well and am having difficulty printing them. Any other ideas?
– Qhapaq Qowi
Feb 23 at 0:00
@QhapaqQowi Your syntax for setting a variable is incorrect. It wouldn't even be correct for a POSIX shell like bash. The correct syntax isset fish_emoji_width 2. Note the lack of a dollar or equal sign. Also, if you're having problems with non-ASCII chars in general you should check your locale is correctly set. If you typelocaleyou should see something likeLANG="en_US.UTF-8"; i.e., a UTF-8 locale.
– Kurtis Rader
Feb 24 at 0:00
Wow, well that's embarassing haha. Thank you for the edification! I've been trying to learn more about these things. I updated the locale as you mentioned and it worked!!! Somehow I thought I tried it earlier without success, but I realized that it didn't persist throughout terminal sessions. I've fixed it though, and it behaves properly and persists. Thank you so much; I really appreciate it!
– Qhapaq Qowi
Feb 24 at 4:17
add a comment |
This occurs when fish and your terminal don't agree on the width of specific characters.
It is almost always emoji chars since the width of many emoji code points has changed as the Unicode standard has evolved. Complicating matters are magical code points such as U+FE0F which themselves don't have any width but affect the preceding code point.
The simplest solution is to pick different characters. Alternatively, there are various workarounds you can employ to change how fish and your terminal calculate the width of problematic chars.
See, for example, https://github.com/fish-shell/fish-shell/issues/5583
edited Feb 16 at 2:00
JakeGould
32.2k1098141
answered Feb 15 at 18:48
Kurtis RaderKurtis Rader
72947
This occurs when fish and your terminal don't agree on the width of specific characters.
It is almost always emoji chars since the width of many emoji code points has changed as the Unicode standard has evolved. Complicating matters are magical code points such as U+FE0F which themselves don't have any width but affect the preceding code point.
The simplest solution is to pick different characters. Alternatively, there are various workarounds you can employ to change how fish and your terminal calculate the width of problematic chars.
See, for example, https://github.com/fish-shell/fish-shell/issues/5583
edited Feb 16 at 2:00
JakeGould
32.2k1098141
answered Feb 15 at 18:48
Kurtis RaderKurtis Rader
72947
edited Feb 16 at 2:00
JakeGould
32.2k1098141
edited Feb 16 at 2:00
JakeGould
32.2k1098141
edited Feb 16 at 2:00
JakeGould
32.2k1098141
32.2k1098141
answered Feb 15 at 18:48
Kurtis RaderKurtis Rader
72947
answered Feb 15 at 18:48
Kurtis RaderKurtis Rader
72947
answered Feb 15 at 18:48
Kurtis RaderKurtis Rader
72947
72947
Thanks for the help! I've looked into it, but have been unable to have any success. I'm a total noob at fish and customizing terminals in general. I'm unable to get anything from using wcwidth or fish_emoji_width. After usingset $fish_emoji_width=2it lists a lot of configuration entires, but when echoingfish_emoji_width, it still only prints a whitespace. Also, most unicode characters are not rendering well and am having difficulty printing them. Any other ideas?
– Qhapaq Qowi
Feb 23 at 0:00
@QhapaqQowi Your syntax for setting a variable is incorrect. It wouldn't even be correct for a POSIX shell like bash. The correct syntax isset fish_emoji_width 2. Note the lack of a dollar or equal sign. Also, if you're having problems with non-ASCII chars in general you should check your locale is correctly set. If you typelocaleyou should see something likeLANG="en_US.UTF-8"; i.e., a UTF-8 locale.
– Kurtis Rader
Feb 24 at 0:00
Wow, well that's embarassing haha. Thank you for the edification! I've been trying to learn more about these things. I updated the locale as you mentioned and it worked!!! Somehow I thought I tried it earlier without success, but I realized that it didn't persist throughout terminal sessions. I've fixed it though, and it behaves properly and persists. Thank you so much; I really appreciate it!
– Qhapaq Qowi
Feb 24 at 4:17
add a comment |
Thanks for the help! I've looked into it, but have been unable to have any success. I'm a total noob at fish and customizing terminals in general. I'm unable to get anything from using wcwidth or fish_emoji_width. After usingset $fish_emoji_width=2it lists a lot of configuration entires, but when echoingfish_emoji_width, it still only prints a whitespace. Also, most unicode characters are not rendering well and am having difficulty printing them. Any other ideas?
– Qhapaq Qowi
Feb 23 at 0:00
@QhapaqQowi Your syntax for setting a variable is incorrect. It wouldn't even be correct for a POSIX shell like bash. The correct syntax isset fish_emoji_width 2. Note the lack of a dollar or equal sign. Also, if you're having problems with non-ASCII chars in general you should check your locale is correctly set. If you typelocaleyou should see something likeLANG="en_US.UTF-8"; i.e., a UTF-8 locale.
– Kurtis Rader
Feb 24 at 0:00
Wow, well that's embarassing haha. Thank you for the edification! I've been trying to learn more about these things. I updated the locale as you mentioned and it worked!!! Somehow I thought I tried it earlier without success, but I realized that it didn't persist throughout terminal sessions. I've fixed it though, and it behaves properly and persists. Thank you so much; I really appreciate it!
– Qhapaq Qowi
Feb 24 at 4:17
Thanks for the help! I've looked into it, but have been unable to have any success. I'm a total noob at fish and customizing terminals in general. I'm unable to get anything from using wcwidth or fish_emoji_width. After using
set $fish_emoji_width=2 it lists a lot of configuration entires, but when echoing fish_emoji_width, it still only prints a whitespace. Also, most unicode characters are not rendering well and am having difficulty printing them. Any other ideas?– Qhapaq Qowi
Feb 23 at 0:00
Thanks for the help! I've looked into it, but have been unable to have any success. I'm a total noob at fish and customizing terminals in general. I'm unable to get anything from using wcwidth or fish_emoji_width. After using
set $fish_emoji_width=2 it lists a lot of configuration entires, but when echoing fish_emoji_width, it still only prints a whitespace. Also, most unicode characters are not rendering well and am having difficulty printing them. Any other ideas?– Qhapaq Qowi
Feb 23 at 0:00
@QhapaqQowi Your syntax for setting a variable is incorrect. It wouldn't even be correct for a POSIX shell like bash. The correct syntax is
set fish_emoji_width 2. Note the lack of a dollar or equal sign. Also, if you're having problems with non-ASCII chars in general you should check your locale is correctly set. If you type locale you should see something like LANG="en_US.UTF-8"; i.e., a UTF-8 locale.– Kurtis Rader
Feb 24 at 0:00
@QhapaqQowi Your syntax for setting a variable is incorrect. It wouldn't even be correct for a POSIX shell like bash. The correct syntax is
set fish_emoji_width 2. Note the lack of a dollar or equal sign. Also, if you're having problems with non-ASCII chars in general you should check your locale is correctly set. If you type locale you should see something like LANG="en_US.UTF-8"; i.e., a UTF-8 locale.– Kurtis Rader
Feb 24 at 0:00
Wow, well that's embarassing haha. Thank you for the edification! I've been trying to learn more about these things. I updated the locale as you mentioned and it worked!!! Somehow I thought I tried it earlier without success, but I realized that it didn't persist throughout terminal sessions. I've fixed it though, and it behaves properly and persists. Thank you so much; I really appreciate it!
– Qhapaq Qowi
Feb 24 at 4:17
Wow, well that's embarassing haha. Thank you for the edification! I've been trying to learn more about these things. I updated the locale as you mentioned and it worked!!! Somehow I thought I tried it earlier without success, but I realized that it didn't persist throughout terminal sessions. I've fixed it though, and it behaves properly and persists. Thank you so much; I really appreciate it!
– Qhapaq Qowi
Feb 24 at 4:17
add a comment |
Thanks for contributing an answer to Super User!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f1405951%2fpowerline-and-fish-how-can-i-remove-the-large-whitespace-between-the-shell-prom%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
You should always include the version of all relevant software in your question. In this case fish and termite.
– Kurtis Rader
Feb 15 at 18:43
2
Welcome to Super User! You can freely edit your own posts but for your protection, this must be done under the original user account. It looks like you registered and created a second account, which will also interfere with your ability to comment within your thread and to accept an answer. See Merge my accounts to get your accounts merged, which will solve the problem.
– fixer1234
Feb 15 at 23:30
Just to echo what @fixer1234 says, you can always edit and comment on your own posts. So if you face an issue as you described in an earlier edit of your question, get the accounts merged.
– JakeGould
Feb 16 at 2:12
Hello, I really appreciate the help. I finally was able to get the accounts merged. Apologies for the delay; I've been really swamped with school projects. I was also wondering if superuser was the right place to ask this question or if I should have picked another site. Additionally, I forgot to mention I'm using the theme "bobthefish" I'll update my post.
– Qhapaq Qowi
Feb 22 at 23:56