vim-latex-devel — Mailing list for developers/maintainers of the vim-latex project

[Vim-latex-devel] Using biblatex with and multiple compilation with pdflatex

[Auguste O. <aug...@gm...>]

Hello,

I've started using latex-suite and I like it very much, but I am getting
some issues.
I'm using Arch Linux with the last vim-latexsuite build (2013-01-26).

1) I am using biblatex with biber (g:Tex_BiberFlavour = "biber") and
latex-suite doesn't handle it, because it decides whether to launch bibtex
or not based on the .aux file, which is not used by biber (it generates a
.bcf file instead). I have found a way to fix this by modifying the line
        if runCount == 0  && Tex_IsPresentInFile('\\bibdata',
mainFileName_root.'.aux' )
in compiler.vim with
        if runCount == 0  && (Tex_IsPresentInFile('\\bibdata',
mainFileName_root.'.aux') || filereadable(mainFileName_root.'.bcf') )
to test if there is a .bcf file in the directory.

2) The previous fix works nice with a dvi output, but when I try to
generate a pdf output with :TTarget pdf it doesn't work. I set
g:Tex_MultipleCompileFormat to "pdf,dvi" but the compiler is always ran
only one time.
When using dvi I get a message "ran latex n times" in vim statusbar at the
end, but not when using pdf, even when there isn't any error. So it seems
that the function Tex_CompileMultipleTimes is not even called and I can't
find any reason for this.

Thank you in advance

Auguste

PS : I apologize for my approximate English

Re: [Vim-latex-devel] f9 completion changes the size of splitted windows

[Hao F. <all...@gm...>]

Hi Yang,

Did you install Python 2.7.3 (32bit) in your computer?
You can also search "<F9> not work vim latex suite" via google and
probability get the answer.

Best Regards,
Hao Fang



On Wed, Mar 20, 2013 at 2:45 AM, YANG LINCHANG <lin...@gm...>wrote:

> I also want to report another issue about F9 in splitted window
>
> Once I open Voom in one splitted window to see the structure of my text,
> and press F9 after \cite{ in the main window, then  I choose the reference,
> but after that, the citation will not be completed, just leaving \cite{ as
> start.
> regards
>
>
> On Fri, Mar 8, 2013 at 12:21 AM, Peng Shao <sha...@gm...> wrote:
>
>> Hi. Thanks for reading my question. I noticed that if I have two splitted
>> windows in vim and the sizesof them have been adjusted manually for easy
>> reading, say one has 10 more lines than the other, then after F9 completes
>> inserting a citation, the two windows would restore to their original equal
>> size, so I have to manually adjust the size again. Is there anyway to let
>> F9 not change the size of already-opened windows?
>>
>> Thanks.
>>
>> Peng
>>
>>
>> ------------------------------------------------------------------------------
>> Symantec Endpoint Protection 12 positioned as A LEADER in The Forrester
>> Wave(TM): Endpoint Security, Q1 2013 and "remains a good choice" in the
>> endpoint security space. For insight on selecting the right partner to
>> tackle endpoint security challenges, access the full report.
>> http://p.sf.net/sfu/symantec-dev2dev
>> _______________________________________________
>> Vim-latex-devel mailing list
>> Vim...@li...
>> https://lists.sourceforge.net/lists/listinfo/vim-latex-devel
>>
>>
>
>
> ------------------------------------------------------------------------------
> Everyone hates slow websites. So do we.
> Make your web apps faster with AppDynamics
> Download AppDynamics Lite for free today:
> http://p.sf.net/sfu/appdyn_d2d_mar
> _______________________________________________
> Vim-latex-devel mailing list
> Vim...@li...
> https://lists.sourceforge.net/lists/listinfo/vim-latex-devel
>
>

Re: [Vim-latex-devel] f9 completion changes the size of splitted windows

[YANG L. <lin...@gm...>]

I also want to report another issue about F9 in splitted window

Once I open Voom in one splitted window to see the structure of my text,
and press F9 after \cite{ in the main window, then  I choose the reference,
but after that, the citation will not be completed, just leaving \cite{ as
start.
regards


On Fri, Mar 8, 2013 at 12:21 AM, Peng Shao <sha...@gm...> wrote:

> Hi. Thanks for reading my question. I noticed that if I have two splitted
> windows in vim and the sizesof them have been adjusted manually for easy
> reading, say one has 10 more lines than the other, then after F9 completes
> inserting a citation, the two windows would restore to their original equal
> size, so I have to manually adjust the size again. Is there anyway to let
> F9 not change the size of already-opened windows?
>
> Thanks.
>
> Peng
>
>
> ------------------------------------------------------------------------------
> Symantec Endpoint Protection 12 positioned as A LEADER in The Forrester
> Wave(TM): Endpoint Security, Q1 2013 and "remains a good choice" in the
> endpoint security space. For insight on selecting the right partner to
> tackle endpoint security challenges, access the full report.
> http://p.sf.net/sfu/symantec-dev2dev
> _______________________________________________
> Vim-latex-devel mailing list
> Vim...@li...
> https://lists.sourceforge.net/lists/listinfo/vim-latex-devel
>
>

Re: [Vim-latex-devel] Weird shortcut problem

[Rohit P. <kn...@ya...>]

The problem has been solved. It occurred because backspacing was not allowed over the start of the insert. It would appear that latex suite goes into insert then backspaces over the typed stuff and then replaces it with the new text which caused the problem since it wasn't able to delete the shortcut keys and simply added the new text causing it to appear as it did. The following line in .vimrc solved the problem


set backspace=2




________________________________
 From: Rohit Patel <kn...@ya...>
To: "vim...@li..." <vim...@li...> 
Sent: Monday, 11 March 2013 5:48 PM
Subject: [Vim-latex-devel]  Weird shortcut problem
 

This problem suddenly cropped up after a OS reinstall (and obviously a clean install of vim and the latex-suite).

`a now expands to `a\alpha
`b to `b\beta

even the custom maps expand with the map keys ahead of the expanded text. This has obviously made vim-latex entirely useful for me and is an emergency situation since I'm having to use alternate text editor which is an unfathomable pain for me!!!

Thanks in advance for the help. Quick resolution will be immensely helpful.
------------------------------------------------------------------------------
Symantec Endpoint Protection 12 positioned as A LEADER in The Forrester  
Wave(TM): Endpoint Security, Q1 2013 and "remains a good choice" in the  
endpoint security space. For insight on selecting the right partner to 
tackle endpoint security challenges, access the full report. 
http://p.sf.net/sfu/symantec-dev2dev
_______________________________________________
Vim-latex-devel mailing list
Vim...@li...
https://lists.sourceforge.net/lists/listinfo/vim-latex-devel

[Vim-latex-devel] Weird shortcut problem

[Rohit P. <kn...@ya...>]

This problem suddenly cropped up after a OS reinstall (and obviously a clean install of vim and the latex-suite).

`a now expands to `a\alpha
`b to `b\beta

even the custom maps expand with the map keys ahead of the expanded text. This has obviously made vim-latex entirely useful for me and is an emergency situation since I'm having to use alternate text editor which is an unfathomable pain for me!!!

Thanks in advance for the help. Quick resolution will be immensely helpful.

[Vim-latex-devel] f9 completion changes the size of splitted windows

[Peng S. <sha...@gm...>]

Hi. Thanks for reading my question. I noticed that if I have two splitted
windows in vim and the sizesof them have been adjusted manually for easy
reading, say one has 10 more lines than the other, then after F9 completes
inserting a citation, the two windows would restore to their original equal
size, so I have to manually adjust the size again. Is there anyway to let
F9 not change the size of already-opened windows?

Thanks.

Peng

Re: [Vim-latex-devel] breqn

[Gerd W. <ger...@ma...>]

Dear Marc,

this is not a problem of vim-latexsuite, but of the syntax file of vim 
for tex. It is typically located in a location like

/usr/share/vim/vim73/syntax/tex.vim

However, the best solution would be to create a file

.vim/syntax/tex/breqn.vim

which contains the highlighting information for breqn. This can be 
accomplished with something like

call TexNewMathZone("breqnA","dmath",0)

Imho, the first argument should be a unique identifier, see also the 
above tex.vim file.


Best regards
Gerd



On 02/27/2013 09:47 PM, Marc Maetz wrote:
> Dear List,
>
> I'm using the package breqn (automatic line breaking of displayed
> equations) together with vim-latexsuite. Its environments (dmath,
> dgroup, dseries, darray) are not implemented in the ftplugin so all
> underscores and carets are colored red. What is the solution for this?
>
> Best,
> Marc
>
> ------------------------------------------------------------------------------
> Everyone hates slow websites. So do we.
> Make your web apps faster with AppDynamics
> Download AppDynamics Lite for free today:
> http://p.sf.net/sfu/appdyn_d2d_feb
> _______________________________________________
> Vim-latex-devel mailing list
> Vim...@li...
> https://lists.sourceforge.net/lists/listinfo/vim-latex-devel
>

[Vim-latex-devel] breqn

[Marc M. <mar...@gm...>]

Dear List,

I'm using the package breqn (automatic line breaking of displayed 
equations) together with vim-latexsuite. Its environments (dmath, 
dgroup, dseries, darray) are not implemented in the ftplugin so all 
underscores and carets are colored red. What is the solution for this?

Best,
Marc

Re: [Vim-latex-devel] slow open in gvim

[André G. <ga...@we...>]

Am 27.02.2013 09:00, schrieb Gerd Wachsmuth:
> and watch the debug file while loading your tex file.

Hi Gerd,

it seems to do some kind of package scanning which I disabled by setting
    let g:Tex_PackagesMenu = 0
in .vimrc. This reduces the startup time to 3.5s (from 7s) and I think I
can live with this ;).

Thx for helping!

  André

-- 
Homepage   http://page.math.tu-berlin.de/~gaul
Twitter    https://twitter.com/#!/andrenarchy
Diaspora   https://diasp.org/u/andrenarchy
           (you won't find me on facebook!)
Jabber     ga...@we...
PGP Key    0xDA246182

Re: [Vim-latex-devel] slow open in gvim

[Gerd W. <ger...@ma...>]

I cannot reproduce this behaviour. You might want to set

let g:Tex_Debug = 1
let g:Tex_DebugLog = "vim-latex-suite.log"

in .vim/ftplugin/tex.vim

and watch the debug file while loading your tex file.


Regards
Gerd


On 02/25/2013 10:34 AM, André Gaul wrote:
> Am 22.02.2013 16:15, schrieb Mirko Hessel-von Molo:
>> Did you try to start gvim with -V[N] option (see man page) to see what it
>> is doing during the seven seconds?
>
> Hi Mirko,
>
> I tried -V but it does not seem to produce valuable information most of
> the time. However, I ran
>     gvim --startuptime startup.log funcall.tex
> which results in this output:
>     http://pastebin.com/54dtJTvt
>
> Do you have any further ideas or is anybody able to reproduce this behavior?
>
> Ciao,
> André
>

Re: [Vim-latex-devel] slow open in gvim

[André G. <ga...@we...>]

Am 22.02.2013 16:15, schrieb Mirko Hessel-von Molo:
> Did you try to start gvim with -V[N] option (see man page) to see what it
> is doing during the seven seconds?

Hi Mirko,

I tried -V but it does not seem to produce valuable information most of
the time. However, I ran
   gvim --startuptime startup.log funcall.tex
which results in this output:
   http://pastebin.com/54dtJTvt

Do you have any further ideas or is anybody able to reproduce this behavior?

Ciao,
André

-- 
Homepage   http://page.math.tu-berlin.de/~gaul
Twitter    https://twitter.com/#!/andrenarchy
Diaspora   https://diasp.org/u/andrenarchy
           (you won't find me on facebook!)
Jabber     ga...@we...
PGP Key    0xDA246182

Re: [Vim-latex-devel] everymath color is not working inside eqnarray

[Alessandro P. <ale...@la...>]

2013/2/24 Rudra Banerjee <rud...@ao...>:
> In my preamble, I have
> \everymath{\color{pmsGreen}}
> \setbeamercolor{normal text}{fg=pms286}
>
> Now, if I write something in inline mathmode ($$), its following
> \everymath; but if it is inside equation environment, its just in normal
> text.
>
> eg,
> \begin{equation}
>     A=B
> \end{equation}
>  $A=J$
> in this block, A=B is in pms286 color, A=J is in pmsGreen.
>
> What should I do?
>
> NB:Though  it is not really associated with vim-latex, I have a problem
> to solve. So, please forgive me cross-posting both in vim-use and
> vim-latex

Actually, this isn't vim related at all. You would be better off
looking in some LaTeX related forum, like the one on StackExchange
[1]. Still, here are a few pointers, though it doesn't seem to be a
trivial task to achieve what you want (at least if you use any amsmath
display environments).

- It seems that the '\everymath' command works only for inline math
mode [2], while '\everydisplay' works, well, for display math mode.
- It looks like the '\everydisplay' command doesn't play well with (at
least) some amsmath display environments [3] [4].
- Moreover, something not directly math related seems to be using math
mode, too, so '\everymath' could colour  more things than you expect
it to [5].

These are just my two cents, based on a quick search. Hope it helps.
Alessandro

[1] http://tex.stackexchange.com/
[2] https://en.wikibooks.org/wiki/TeX/everymath
[3] http://tex.stackexchange.com/questions/13592/why-does-everydisplay-conflict-with-gather-and-multline
[4] http://tex.stackexchange.com/questions/37319/how-do-i-get-different-colors-for-math-and-for-text
[5] http://tex.stackexchange.com/questions/48191/is-there-a-way-to-color-only-real-math-in-pdflatex

[Vim-latex-devel] everymath color is not working inside eqnarray

[Rudra B. <rud...@ao...>]

In my preamble, I have
\everymath{\color{pmsGreen}}
\setbeamercolor{normal text}{fg=pms286}

Now, if I write something in inline mathmode ($$), its following
\everymath; but if it is inside equation environment, its just in normal
text.

eg,
\begin{equation}
    A=B
\end{equation}
 $A=J$
in this block, A=B is in pms286 color, A=J is in pmsGreen.

What should I do?

NB:Though  it is not really associated with vim-latex, I have a problem
to solve. So, please forgive me cross-posting both in vim-use and
vim-latex

[Vim-latex-devel] slow open in gvim

[André G. <ga...@we...>]

Hey List,

I observe that gvim is very slow when opening tex files if the
latex-suite plugin is active. An example tex file which takes ~7 seconds
to load can be found here: [1]. My .vimrc only contains the line
    filetype plugin on
and the .vim folder only contains the latex-suite files (snapshot
2013-01-16).

I also posted this on stackoverflow [2], but so far I've not much
insight. ;) Do you have any idea what might be wrong here?

thx,
André

[1]
https://bitbucket.org/andrenarchy/funcall/raw/25d83535b4839ae1598a620b4cb7315a467ccc4b/funcall.tex
[2]
http://stackoverflow.com/questions/15024035/vim-gvim-startup-very-slow-with-latex-suite
-- 
Homepage   http://page.math.tu-berlin.de/~gaul
Twitter    https://twitter.com/#!/andrenarchy
Diaspora   https://diasp.org/u/andrenarchy
           (you won't find me on facebook!)
Jabber     ga...@we...
PGP Key    0xDA246182

[Vim-latex-devel] [ vim-latex-Bugs-3605543 ] Macros are not replaced

[SourceForge.net <no...@so...>]

Bugs item #3605543, was opened at 2013-02-21 06:47
Message generated for change (Tracker Item Submitted) made by bugeyefix
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=466456&aid=3605543&group_id=52322

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: None
Group: None
Status: Open
Resolution: None
Priority: 5
Private: No
Submitted By: Will Nicht (bugeyefix)
Assigned to: Nobody/Anonymous (nobody)
Summary: Macros are not replaced

Initial Comment:
Using macros generates the right latex code but the macro itself is not removed. For example the macro EIT gives:

EIT\begin{itemize}
     \item
\end{itemize}<++>

or

`8\infty


----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=466456&aid=3605543&group_id=52322

Re: [Vim-latex-devel] Problem pasting between files

[Gerd W. <ger...@ma...>]

Hi,

I can't reproduce this behaviour. All registers ("", "*, "+) are not 
affected by opening a new (g)vim session (with or without latex-suite). 
I'm using my own version of latex-suite 
(https://github.com/gerw/vim-latex-suite).

Regards
Gerd


On 02/09/2013 09:18 PM, David Woodfall wrote:
> On (09/02/13 20:53), Bodo Graumann <ma...@bo...> put forth the proposition:
>> Indeed I'm using Gentoo linux and the rather old vim-latex version
>> 1.8.23.20110214. Could very well be that this is a known and fixed
>> issue. Btw. only the "* register is affected, not the "+ one.
>>
>> Bodo
>
> Slackware here.
>
> Vim 7.3.645
> vim-latex-1.8.23-20121116.784-git1c17b37.tar.gz
>
>> Am Sat, 9 Feb 2013 20:41:12 +0100
>> schrieb Alessandro Pezzoni <ale...@la...>:
>>
>> | 2013/2/9 Bodo Graumann <ma...@bo...>:
>> | > I can confirm something like this.
>> | > Usually if I select some text anywhere (in any application), then
>> | > open gvim, open a file, I can paste the original selection right
>> | > into it. But not so with .tex-files. When those are opened, the
>> | > copy-paste-buffer is overwritten with the content of the file. So
>> | > when it’s a new .tex file a single empty line would be pasted.
>> |
>> | I can't reproduce this here (on ArchLinux). Both "* and "+ registers
>> | are set to the current clipboard values when opening both tex and
>> | non-tex files with gvim. Does this happen with any tex file? I gather
>> | you are using Linux? If so, which distribution?
>> |
>> | Alessandro
>
> ------------------------------------------------------------------------------
> Free Next-Gen Firewall Hardware Offer
> Buy your Sophos next-gen firewall before the end March 2013
> and get the hardware for free! Learn more.
> http://p.sf.net/sfu/sophos-d2d-feb
> _______________________________________________
> Vim-latex-devel mailing list
> Vim...@li...
> https://lists.sourceforge.net/lists/listinfo/vim-latex-devel
>

Re: [Vim-latex-devel] Questions about adding options of ps2pdf while Windows

[Hao F. <all...@gm...>]

Hi Alessandro,

Thanks for your help.
I tried to use double quotes while escaping the '#' with '\', then it again
shows
"E194: No alternate file name to substitute for '#'".

Anyway, I think I can still achieve my goal by avoid using options in
ps2pdf.

Best Regards,
Hao Fang



On Sat, Feb 9, 2013 at 3:32 AM, Alessandro Pezzoni <
ale...@la...> wrote:

> 2013/2/9 Hao Fang <all...@gm...>:
> > If I use
> > " :!ps2pdf -sPAPERSIZE\#letter document.ps document.pdf "
> > (adding '\' before '#'), then it works.
> > [...]
> > However, if I set it in tex.vim, i.e.,
> > let g:Tex_CompileRule_pdf = 'ps2pdf -sPAPERSIZE\#letter $*.ps $.pdf'
> > It will actually run
> > :!ps2pdf -sPAPERSIZE\#letter document.ps document.pdf > C:/Users/...
>
> Dear Hao Fang,
> escaping the '#' (i.e. adding '\' in front of it) should be indeed the
> way to go. I don't know at which point in the code the substitutions
> are made, but you could try changing the quotes with double quotes
> (i.e. put " instead of '). You could have to escape some other
> characters in that case, though.
>
> If you don't need the .dvi or the .ps, you could also try to bypass
> the issue entirely by compiling with pdflatex (this could possibly
> require some small tweaks in your source file, though).
>
> Alessandro
>
>

Re: [Vim-latex-devel] Add a placeholder in my keymap

[Rudra B. <rud...@ao...>]

Ah...thats great! 
Thanks
On Sun, 2013-02-10 at 10:57 +0100, Bodo Graumann wrote:
> Why don’t you use
> 
> call IMAP('FRM', "\\begin{frame}^M\frametitle{<++>}^M<++>^M\\end{frame}<++>", 'tex')
> 
> possibly into ~/.vim/after/ftplugin/tex/latex_suite.vim
> 
> Am Sun, 10 Feb 2013 09:39:16 +0000
> schrieb Rudra Banerjee <rud...@ao...>:
> 
> | Dear friends,
> | I have added this keymap in my vimrc:
> | nmap <C-F12> :call Insrt_frame()
> | function! Insrt_frame()
> |   :put='\begin{frame}'
> |   :put='\frametitle{<++>}'
> |   :put=''
> |   :put='\end{frame}'
> | endfunction
> | 
> | I am trying to put the cursor on the \frametitle.
> | How can I achieve this?
> | 
> | 
> | ------------------------------------------------------------------------------
> | Free Next-Gen Firewall Hardware Offer
> | Buy your Sophos next-gen firewall before the end March 2013 
> | and get the hardware for free! Learn more.
> | http://p.sf.net/sfu/sophos-d2d-feb
> | _______________________________________________
> | Vim-latex-devel mailing list
> | Vim...@li...
> | https://lists.sourceforge.net/lists/listinfo/vim-latex-devel
> | 

Re: [Vim-latex-devel] Add a placeholder in my keymap

[Alessandro P. <ale...@la...>]

2013/2/10 Rudra Banerjee <rud...@ao...>:
> Dear friends,
> I have added this keymap in my vimrc:
> nmap <C-F12> :call Insrt_frame()
> function! Insrt_frame()
>   :put='\begin{frame}'
>   :put='\frametitle{<++>}'
>   :put=''
>   :put='\end{frame}'
> endfunction
>
> I am trying to put the cursor on the \frametitle.
> How can I achieve this?

Dear Rudra Banerjee,
adding the following to your .vimrc (preferably in an autocmd) instead
of your mapping will achieve what you're looking for:

let g:Tex_Env_frame="\\begin{frame}\<CR>\\frametitle{<++>}\<CR><++>\<CR>\\end{frame}<++>"
nmap <C-F12> iframe<F5>

For more information, have a look here [1].

Alessandro

[1] http://vim-latex.sourceforge.net/documentation/latex-suite/customizing-macros.html#Tex_Env_name

Re: [Vim-latex-devel] Add a placeholder in my keymap

[Bodo G. <ma...@bo...>]

Why don’t you use

call IMAP('FRM', "\\begin{frame}^M\frametitle{<++>}^M<++>^M\\end{frame}<++>", 'tex')

possibly into ~/.vim/after/ftplugin/tex/latex_suite.vim

Am Sun, 10 Feb 2013 09:39:16 +0000
schrieb Rudra Banerjee <rud...@ao...>:

| Dear friends,
| I have added this keymap in my vimrc:
| nmap <C-F12> :call Insrt_frame()
| function! Insrt_frame()
|   :put='\begin{frame}'
|   :put='\frametitle{<++>}'
|   :put=''
|   :put='\end{frame}'
| endfunction
| 
| I am trying to put the cursor on the \frametitle.
| How can I achieve this?
| 
| 
| ------------------------------------------------------------------------------
| Free Next-Gen Firewall Hardware Offer
| Buy your Sophos next-gen firewall before the end March 2013 
| and get the hardware for free! Learn more.
| http://p.sf.net/sfu/sophos-d2d-feb
| _______________________________________________
| Vim-latex-devel mailing list
| Vim...@li...
| https://lists.sourceforge.net/lists/listinfo/vim-latex-devel
| 

[Vim-latex-devel] Add a placeholder in my keymap

[Rudra B. <rud...@ao...>]

Dear friends,
I have added this keymap in my vimrc:
nmap <C-F12> :call Insrt_frame()
function! Insrt_frame()
  :put='\begin{frame}'
  :put='\frametitle{<++>}'
  :put=''
  :put='\end{frame}'
endfunction

I am trying to put the cursor on the \frametitle.
How can I achieve this?

Re: [Vim-latex-devel] Problem pasting between files

[David W. <da...@da...>]

On (09/02/13 20:53), Bodo Graumann <ma...@bo...> put forth the proposition:
>Indeed I'm using Gentoo linux and the rather old vim-latex version
>1.8.23.20110214. Could very well be that this is a known and fixed
>issue. Btw. only the "* register is affected, not the "+ one.
>
>Bodo

Slackware here. 

Vim 7.3.645 
vim-latex-1.8.23-20121116.784-git1c17b37.tar.gz

>Am Sat, 9 Feb 2013 20:41:12 +0100
>schrieb Alessandro Pezzoni <ale...@la...>:
>
>| 2013/2/9 Bodo Graumann <ma...@bo...>:
>| > I can confirm something like this.
>| > Usually if I select some text anywhere (in any application), then
>| > open gvim, open a file, I can paste the original selection right
>| > into it. But not so with .tex-files. When those are opened, the
>| > copy-paste-buffer is overwritten with the content of the file. So
>| > when it’s a new .tex file a single empty line would be pasted.
>|
>| I can't reproduce this here (on ArchLinux). Both "* and "+ registers
>| are set to the current clipboard values when opening both tex and
>| non-tex files with gvim. Does this happen with any tex file? I gather
>| you are using Linux? If so, which distribution?
>|
>| Alessandro

Re: [Vim-latex-devel] Problem pasting between files

[Bodo G. <ma...@bo...>]

Indeed I'm using Gentoo linux and the rather old vim-latex version 
1.8.23.20110214. Could very well be that this is a known and fixed
issue. Btw. only the "* register is affected, not the "+ one.

Bodo

Am Sat, 9 Feb 2013 20:41:12 +0100
schrieb Alessandro Pezzoni <ale...@la...>:

| 2013/2/9 Bodo Graumann <ma...@bo...>:
| > I can confirm something like this.
| > Usually if I select some text anywhere (in any application), then
| > open gvim, open a file, I can paste the original selection right
| > into it. But not so with .tex-files. When those are opened, the
| > copy-paste-buffer is overwritten with the content of the file. So
| > when it’s a new .tex file a single empty line would be pasted.
| 
| I can't reproduce this here (on ArchLinux). Both "* and "+ registers
| are set to the current clipboard values when opening both tex and
| non-tex files with gvim. Does this happen with any tex file? I gather
| you are using Linux? If so, which distribution?
| 
| Alessandro
| 
| 
| ------------------------------------------------------------------------------
| Free Next-Gen Firewall Hardware Offer
| Buy your Sophos next-gen firewall before the end March 2013 
| and get the hardware for free! Learn more.
| http://p.sf.net/sfu/sophos-d2d-feb
| _______________________________________________
| Vim-latex-devel mailing list
| Vim...@li...
| https://lists.sourceforge.net/lists/listinfo/vim-latex-devel
| 

Re: [Vim-latex-devel] Problem pasting between files

[Alessandro P. <ale...@la...>]

2013/2/9 Bodo Graumann <ma...@bo...>:
> I can confirm something like this.
> Usually if I select some text anywhere (in any application), then open
> gvim, open a file, I can paste the original selection right into it.
> But not so with .tex-files. When those are opened, the copy-paste-buffer
> is overwritten with the content of the file. So when it’s a new .tex
> file a single empty line would be pasted.

I can't reproduce this here (on ArchLinux). Both "* and "+ registers
are set to the current clipboard values when opening both tex and
non-tex files with gvim. Does this happen with any tex file? I gather
you are using Linux? If so, which distribution?

Alessandro

Re: [Vim-latex-devel] Problem pasting between files

[Devendra G. <dev...@gm...>]

On 02/09/2013 09:49 PM, Alessandro Pezzoni wrote:
> 2013/2/9 David Woodfall <da...@da...>:
>> On (09/02/13 13:02), David Woodfall <da...@da...> put forth the proposition:
>>> On (09/02/13 13:39), Alessandro Pezzoni <ale...@la...> put forth the proposition:
>>>>> Thanks Alessandro. It's a bit strange how it works with other files
>>>>> without need to add "*, but at least I know how now.
>>>> The first thing I can think of is that if you select text with your
>>>> mouse in X11 it usually gets copied to the clipboard right away. Note
>>>> that this works for vim (in a terminal), but not for gvim, so one
>>>> possible explanation would be if you are used to edit files with vim,
>>>> but edit tex files from gvim (which I do).
>>> No, I'm using only vim commands d and p
>> Make that y and p
> Ok, so if I understand you correctly, usually if you yank (y) some
> text from a file, close vim, then open it on a different file, you can
> paste (p) it back, without using the "* or "+ registers? That sounds
> odd...
>
> Alessandro
I found out about this from David's email today and it works fine for
me for .tex files.

Devendra


>
> ------------------------------------------------------------------------------
> Free Next-Gen Firewall Hardware Offer
> Buy your Sophos next-gen firewall before the end March 2013
> and get the hardware for free! Learn more.
> http://p.sf.net/sfu/sophos-d2d-feb
> _______________________________________________
> Vim-latex-devel mailing list
> Vim...@li...
> https://lists.sourceforge.net/lists/listinfo/vim-latex-devel