On 06/28/2016 02:14, Yuri wrote:
Sorry for the delay.
Unicode characters without the nls option in bash-4.3.46 are still a
problem.
Correction: it was a stray patch in FreeBSD port that made HAVE_ICONV
undefined. Without it iconv is detected fine without nls.
However, I believe this is
On 02/07/2016 13:14, Chet Ramey wrote:
Sorry, I misread the autoconf macro. This isn't the cause. You should
look at config.log to see what happens when configure tests for iconv.
Chet
Sorry for the delay.
Unicode characters without the nls option in bash-4.3.46 are still a
problem.
con
On 2/5/16 5:47 PM, Yuri wrote:
> On 02/05/2016 11:13, Chet Ramey wrote:
>> AM_GNU_GETTEXT is the autoconf macro that adds the --disable-nls option
>> to configure. It handles checking for iconv by calling AM_ICONV. If
>> you disable it by calling configure with --disable-nls, it doesn't look
>> f
On 02/05/2016 11:13, Chet Ramey wrote:
AM_GNU_GETTEXT is the autoconf macro that adds the --disable-nls option
to configure. It handles checking for iconv by calling AM_ICONV. If
you disable it by calling configure with --disable-nls, it doesn't look
for iconv.
Well, this is wrong in the bash
On 2/3/16 4:54 PM, Yuri wrote:
> And why the same escape character is interpreted in two different ways
> within the same piece of software?
Because $'...' is posix (or soon to be) and standardized and PS1
interpretation is historical bash practice.
--
``The lyf so short, the craft so long to l
On 2/3/16 7:54 PM, Yuri wrote:
> On 01/31/2016 13:41, Yuri wrote:
>>
>> What makes bash print unicode charater ascii values?
>
> I found what the problem is:
> --disable-nls causes HAVE_ICONV being undefined and \u feature not work.
AM_GNU_GETTEXT is the autoconf macro that adds the --disabl
On 01/31/2016 13:41, Yuri wrote:
What makes bash print unicode charater ascii values?
I found what the problem is:
--disable-nls causes HAVE_ICONV being undefined and \u feature not work.
This is a bug, because "nls" refers to translations. I usually turn them
off because I don't want t
Yuri wrote:
> On 02/03/2016 14:06, Greg Wooledge wrote:
> > Works for me.
> >
> > wooledg@wooledg:~$ PS1=$'\u2023 \w\$ '
> > ? ~$
> >
> > I just can't show it in this cross-system-X2X-with-different-
> > character-sets
> > setup. But it works for me, on Debian GNU/Linux with
> > LANG=en_US.UTF-8
On 02/03/2016 14:06, Greg Wooledge wrote:
Works for me.
wooledg@wooledg:~$ PS1=$'\u2023 \w\$ '
? ~$
I just can't show it in this cross-system-X2X-with-different-character-sets
setup. But it works for me, on Debian GNU/Linux with LANG=en_US.UTF-8.
I believe you. It does work for you. Just not
On Wed, Feb 03, 2016 at 01:54:39PM -0800, Yuri wrote:
> At least U+2023 is a valid character, it should be printed in utf8 as a
> unicode codepoint. My locale is utf8.
Works for me.
wooledg@wooledg:~$ PS1=$'\u2023 \w\$ '
? ~$
I just can't show it in this cross-system-X2X-with-different-characte
On 02/03/2016 13:13, Chet Ramey wrote:
Sigh. You are mixing two things that perform backslash-escape character
processing. If there is no character corresponding to a particular unicode
value in the current character set, the escape sequence is left unchanged.
So you get through a round of expa
On 2/3/16 3:20 PM, Yuri wrote:
> On 01/31/2016 13:41, Yuri wrote:
>> I have this line in ~/.bashrc:
>> PS1=$'\\[\e[0;38;5;202m\\]\u2514\u2023\\[\e[0m\\] '
>
> This link
> http://unix.stackexchange.com/questions/25903/awesome-symbols-and-characters-in-a-bash-prompt
> says: "Since bash 4.2, you can
On 01/31/2016 13:41, Yuri wrote:
I have this line in ~/.bashrc:
PS1=$'\\[\e[0;38;5;202m\\]\u2514\u2023\\[\e[0m\\] '
This link
http://unix.stackexchange.com/questions/25903/awesome-symbols-and-characters-in-a-bash-prompt
says: "Since bash 4.2, you can use \u followed by 4 hexadecimal digits
On 1/31/16 4:41 PM, Yuri wrote:
> I have this line in ~/.bashrc:
> PS1=$'\\[\e[0;38;5;202m\\]\u2514\u2023\\[\e[0m\\] '
>
> My command prompt looks like this:
> root2514root2023
>
> What makes bash print unicode charater ascii values?
In this case, probably that iconv fails to convert that value
I have this line in ~/.bashrc:
PS1=$'\\[\e[0;38;5;202m\\]\u2514\u2023\\[\e[0m\\] '
My command prompt looks like this:
root2514root2023
What makes bash print unicode charater ascii values?
bash-4.3.42
FreeBSD-10.3
LANG=en_US.UTF-8
terminal is konsole from kde4
Yuri
15 matches
Mail list logo