1. 16 Oct, 2016 1 commit
  2. 15 Oct, 2016 7 commits
  3. 14 Oct, 2016 1 commit
    • Linda_pp's avatar
      startup: Remove 'N files to edit' message. #5481 · 79d77da8
      Linda_pp authored
          When '--embed' passed to command line arguments, stdin and stdout
          are used for IPC. But when multiple files are passed as
          arguments, nvim wrongly sends 'N files to edit' message to its
          stdout. As the result, attaching to process from frontend failed.
          Remove the message because it doesn't fill any purpose.
  4. 13 Oct, 2016 4 commits
  5. 12 Oct, 2016 18 commits
  6. 11 Oct, 2016 4 commits
    • Shougo's avatar
    • James McCoy's avatar
      ui: Fix the call to utf_ambiguous_width · 892f55bd
      James McCoy authored
      `utf_ambiguous_width` expects the Unicode character, but in 9e1c6596 I
      just passed the first UTF-8 byte to the function.  This led to various
      display problems because now many multi-cell characters weren't falling
      into that part of the branch.
      Also, to better align with the existing Vim code, remove the forced
      cursor update.  Setting the flag will cause it to happen in the next
      Thanks to qvacua for all the help investigating the issue!
      Closes #5448
    • James McCoy's avatar
      Merge pull request #5457 from jamessan/wincmd-count · f1bc50d7
      James McCoy authored
      window: Fix cmd_with_count's formatting when sizeof(long) != 8
    • James McCoy's avatar
      window: Fix cmd_with_count's formatting when sizeof(long) != 8 · d545c8e1
      James McCoy authored
      On architectures where `sizeof(long)` != 8, "%" PRId64 will read junk from
      memory.  This was seen on various Debian builds where
      test/functional/legacy/close_count_spec.lua would fail due to `1<C-w>c`
      emitting an error like `E488: Trailing characters: close-87944975647104`.
      Changing the `Prenum` parameter to int64_t ensures it is safe to use
      `"%" PRId64`, and make another small step towards removal of the use of
  7. 10 Oct, 2016 4 commits
    • James McCoy's avatar
      lint · 1dd98a03
      James McCoy authored
    • James McCoy's avatar
      if_cscope: Fix conversion warnings when char defaults to unsigned · 8fd12805
      James McCoy authored
          ../src/nvim/if_cscope.c: In function 'cs_read_prompt':
          ../src/nvim/if_cscope.c:1771:47: warning: comparison is always true due to limited range of data type [-Wtype-limits]
               while ((ch = (char)getc(csinfo[i].fr_fp)) != EOF && ch != CSCOPE_PROMPT[0])
          ../src/nvim/if_cscope.c:1804:14: warning: comparison is always false due to limited range of data type [-Wtype-limits]
                 if (ch == EOF) {
          ../src/nvim/if_cscope.c:1816:14: warning: negative integer implicitly converted to unsigned type [-Wsign-conversion]
                   ch = EOF;
          ../src/nvim/if_cscope.c:1821:12: warning: comparison is always false due to limited range of data type [-Wtype-limits]
               if (ch == EOF)
      Since EOF is -1, it will be converted to a large unsigned value to
      compare with unsigned char and never match.  Use an int to store the
      return from getc so we can safely compare it and, once known to be
      valid, cast it to char when storing it into buf.
      Signed-off-by: default avatarJames McCoy <jamessan@jamessan.com>
    • James McCoy's avatar
      Change constack.cs_flags from char to int · 4192c411
      James McCoy authored
      This fixes the -Wconversion warning when char's type is unsigned.
          ../src/nvim/ex_eval.c: In function 'ex_while':
          ../src/nvim/ex_eval.c:1000:28: warning: conversion to 'char' from 'int' may alter its value [-Wconversion]
                 cstack->cs_lflags &= ~CSL_HAD_LOOP;
      Signed-off-by: default avatarJames McCoy <jamessan@jamessan.com>
    • James McCoy's avatar
      ci: Force unsigned char usage for the 32bit build · cb03517f
      James McCoy authored
      Since C leaves whether char is signed or unsigned up to the implementer,
      there are different defaults on different architectures.
      Forcing unsigned char for one of our CI builds should help catch these
      issues moving forward.
  8. 09 Oct, 2016 1 commit