Le 05/06/2018 à 05:54, John Little a écrit :
On Monday, June 4, 2018 at 5:08:05 PM UTC+12, phkbphkbphkb wrote:
... t_kB is not set on
st (https://st.suckless.org/)
I think it is. I downloaded the st-0.8.1.tar.gz from there, extracted st.info,
ran
tic st.info
TERM=st-256color vim
On Monday, June 4, 2018 at 5:08:05 PM UTC+12, phkbphkbphkb wrote:
> ... t_kB is not set on
> st (https://st.suckless.org/)
I think it is. I downloaded the st-0.8.1.tar.gz from there, extracted st.info,
ran
tic st.info
TERM=st-256color vim -c 'echo _kB'
and it shows ^[[Z. (I ignored
Le 04/06/2018 à 16:23, Christian Brabandt a écrit :
On Mo, 04 Jun 2018, phkbphkbphkb wrote:
Hi,
I'm not sure if it is a bug in vim, but Shift-Tab is not working on my
machine. For example, it clears the line in command mode instead of getting
back to the previous completion.
I solved the
Thanks, Christian.
I wasn't sure it would work, but I figured it was worth asking.
As I mentioned in a comment on the issue, I'm fine with a VIM_TERMINAL variable
so long as it allows me to distinguish when a terminal window is in use.
Thanks, again!
--
--
You received this message from the
On Mo, 04 Jun 2018, Jason Franklin wrote:
> That may be the solution we're looking for, if it's possible. Also, note that
> passing the patch level isn't really necessary since a user can define an
> environment variable on their own for this purpose.
Well the User can also set a environment
> I suppose we can add VIM_TERMINAL for that.
Hey @Bram,
Please take a look at the following issue before simply using an environment
variable:
https://github.com/vim/vim/issues/2981
I've given this some thought, and an environment variable wouldn't work in all
cases.
I'm not sure,
Christian wrote:
> On Mo, 04 Jun 2018, Jason Franklin wrote:
>
> > Unfortunately, $VIM_SERVERNAME is not always available. This happens
> > when Vim is compiled without +clientserver.
>
> Good catch. I did not think of it and I have been using the
> VIM_SERVERNAME environment variable for
Andy Wokula wrote:
> >> Am 01.06.2018 um 08:25 schrieb dmcco...@comcast.net:
> >>> Hello,
> >>>
> >>> I have encountered what appears to be a bug in vim,
> >>> but it might be a feature that I would like to disable.
> >>>
> >>> To reproduce the problem:
> >>>
> >>> Use vim to create a new file,
Christian,
I don't think an environment variable is really going to solve this problem.
I created an issue on github for this idea, you can see my explanation there:
https://github.com/vim/vim/issues/2981
That may be the solution we're looking for, if it's possible. Also, note that
passing the
On Mo, 04 Jun 2018, Jason Franklin wrote:
> Unfortunately, $VIM_SERVERNAME is not always available. This happens
> when Vim is compiled without +clientserver.
Good catch. I did not think of it and I have been using the
VIM_SERVERNAME environment variable for this purpose.
@Bram, can we have
Hey Tim,
This is not as useful because vim can be invoked by many names (e.g., a vi
alias or link).
Also, I don't think this works the way you think. In my vim terminal window, I
don't have a listing for vim in ps output.
Something more robust is needed.
-- JF
--
--
You received this
On 30/05/18 13:48, Jason Franklin wrote:
I would like for bash to be able to discern whether it is being
run with :shell or with :term. I would assume this would need
to be done with an environment variable. Does this feature to
do something like this already exist?
You could look at the
Am 02.06.2018 um 09:29 schrieb Bram Moolenaar:
Andy Wokula wrote:
Am 01.06.2018 um 08:25 schrieb dmcco...@comcast.net:
Hello,
I have encountered what appears to be a bug in vim,
but it might be a feature that I would like to disable.
To reproduce the problem:
Use vim to create a new file,
Hey Christian,
Unfortunately, $VIM_SERVERNAME is not always available. This happens when Vim
is compiled without +clientserver.
Thanks,
Jason
--
--
You received this message from the "vim_use" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more
On Mi, 30 Mai 2018, Jason Franklin wrote:
> I would like for bash to be able to discern whether it is being run with
> :shell or with :term. I would assume this would need to be done with an
> environment variable. Does this feature to do something like this already
> exist?
Check for the
On Mo, 04 Jun 2018, phkbphkbphkb wrote:
> Hi,
>
> I'm not sure if it is a bug in vim, but Shift-Tab is not working on my
> machine. For example, it clears the line in command mode instead of getting
> back to the previous completion.
>
> I solved the problem using the following workaround
Den måndag 4 juni 2018 kl. 13:17:29 UTC+2 skrev Erik Christiansen:
> On 04.06.18 02:44, Patrik Iselind wrote:
> > Hi,
> >
> > I have a use case that I run into quite often, but cannot find a solution
> > for. So I ask here.
> >
> > I have an example document
> > ```example document
> > foo bar
I'm actually beginning to think that this isn't possible. Even if I was able
to distinguish at the level of the child shell, I don't think I could continue
that for, say, a subshell of that shell.
In other words, knowing something is a job with an environment variable won't
tell you anything
Hey Martin,
This doesn't actually help me. The 'shell' setting is used for both types of
shell sessions spawned from Vim.
I'm looking to be able to distinguish between bash sessions run in a Vim
terminal window or in a normal xterm.
For example, I would like a different prompt if bash is
On 04.06.18 02:44, Patrik Iselind wrote:
> Hi,
>
> I have a use case that I run into quite often, but cannot find a solution
> for. So I ask here.
>
> I have an example document
> ```example document
> foo bar
> ```
>
> My cursor is at the first o character in foo. I would like to change
> foo
Hi,
I have a use case that I run into quite often, but cannot find a solution for.
So I ask here.
I have an example document
```example document
foo bar
```
My cursor is at the first o character in foo. I would like to change foo to
foolish, so the document becomes
```example document
foolish
Hi Jason,
You can set `set shell=/bin/bash\ --rcfile=$HOME/.vim_bashrc` and set the
environment variable there (and source your ~/.bashrc file as well).
Best regards,
Marcin Szamotulski
Sent with ProtonMail Secure Email.
‐‐‐ Original Message ‐‐‐
On May 30, 2018 4:06 PM, Jason
22 matches
Mail list logo
