You are viewing an historical archive of past issues. Please report new issues to the appropriate project issue tracker on GitHub.

Support ticket #1978: Installation of command-t by non-interactive shell

Kind support ticket
Product Command-T
When Created , updated
Status closed
Reporter anonymous
Tags no tags

Description

Hi,

I am trying to package command-t for Fedora, however I am not able to install it non-interactively. I am executing the following command from build script: vim -c 'so % | q' /builddir/build/SOURCES/command-t-1.3.1.vba, unfortunately hangs (see the log below). I suspect the script to wait for confirming "next", the same way as when it is installed interactively. Thank you for you help. 

Vim: Warning: Output is not to a terminal
Vim: Warning: Input is not from a terminal
[?1h="~/build/SOURCES/command-t-1.3.1.vba" 3213L, 121299C" Vimball Archiver by Charles E. Campbell, Jr., Ph.D.
UseVimball
finish
+--332 lines: ruby/command-t/controller.rb -------------------------------------+-- 34 lines: ruby/command-t/extconf.rb ----------------------------------------+-- 37 lines: ruby/command-t/finder/buffer_finder.rb ---------------------------+-- 37 lines: ruby/command-t/finder/file_finder.rb -----------------------------+-- 37 lines: ruby/command-t/finder/jump_finder.rb -----------------------------+-- 54 lines: ruby/command-t/finder.rb -----------------------------------------+--392 lines: ruby/command-t/match_window.rb -----------------------------------+--167 lines: ruby/command-t/prompt.rb -----------------------------------------+-- 44 lines: ruby/command-t/scanner/buffer_scanner.rb -------------------------+--103 lines: ruby/command-t/scanner/file_scanner.rb ---------------------------+-- 55 lines: ruby/command-t/scanner/jump_scanner.rb ---------------------------+-- 30 lines: ruby/command-t/scanner.rb ----------------------------------------+-- 79 lines: ruby/command-t/settings.rb ---------------------------------------+-- 44 lines: ruby/command-t/stub.rb -------------------------------------------+-- 42 lines: ruby/command-t/vim/path_utilities.rb -----------------------------+-- 34 lines: ruby/command-t/vim/screen.rb -------------------------------------+-- 40 lines: ruby/command-t/vim/window.rb -------------------------------------+-- 53 lines: ruby/command-t/vim.rb --------------------------------------------+-- 67 lines: ruby/command-t/ext.c ---------------------------------------------+--191 lines: ruby/command-t/match.c -------------------------------------------***vimball*** Source this file to extract it! (:so %)
Vimball Archive
extracted <ruby/command-t/controller.rb>: 330 lines
wrote /builddir/.vim/ruby/command-t/controller.rb
extracted <ruby/command-t/extconf.rb>: 32 lines
wrote /builddir/.vim/ruby/command-t/extconf.rb
extracted <ruby/command-t/finder/buffer_finder.rb>: 35 lines
wrote /builddir/.vim/ruby/command-t/finder/buffer_finder.rb
extracted <ruby/command-t/finder/file_finder.rb>: 35 lines
wrote /builddir/.vim/ruby/command-t/finder/file_finder.rb
extracted <ruby/command-t/finder/jump_finder.rb>: 35 lines
wrote /builddir/.vim/ruby/command-t/finder/jump_finder.rb
extracted <ruby/command-t/finder.rb>: 52 lines
wrote /builddir/.vim/ruby/command-t/finder.rb
extracted <ruby/command-t/match_window.rb>: 390 lines
wrote /builddir/.vim/ruby/command-t/match_window.rb
extracted <ruby/command-t/prompt.rb>: 165 lines
wrote /builddir/.vim/ruby/command-t/prompt.rb
extracted <ruby/command-t/scanner/buffer_scanner.rb>: 42 lines
wrote /builddir/.vim/ruby/command-t/scanner/buffer_scanner.rb
extracted <ruby/command-t/scanner/file_scanner.rb>: 101 lines
wrote /builddir/.vim/ruby/command-t/scanner/file_scanner.rb
extracted <ruby/command-t/scanner/jump_scanner.rb>: 53 lines

Comments

  1. Greg Hurrell

    In general I'm not very happy with Vimballs as an installation mechanism. As you've noted it seems to be pausing midway through, and I've found that occasionally it will mysteriously install only a subset of the files in the archive (installing a second time usually fills in the gaps).

    There's nothing special about the Vimball format though. Using a simple tarball of the files would probably be much more reliable.

  2. Vit Ondruch

    Actually, I would be happy with simple tarball, but where to get one, since there are just links to the vimballs

  3. Greg Hurrell

    All the releases in the Git repo are tagged, so you could generate a tar ball with git archive.

  4. Vit Ondruch

    Thank you for the tip. It might work. I realized that you are providing also gemified version, which might work as well.

  5. Greg Hurrell

    Status changed:

    • From: new
    • To: closed
Add a comment

Comments are now closed for this issue.

Menu