1. 05 Jan, 2019 6 commits
  2. 23 Jul, 2018 1 commit
  3. 14 Jun, 2018 2 commits
  4. 01 Nov, 2016 4 commits
  5. 27 Oct, 2016 1 commit
  6. 25 Oct, 2016 1 commit
  7. 22 Oct, 2016 1 commit
    • mrBliss's avatar
      Handle comments when indenting method chains · fba77143
      mrBliss authored
      Previously, indentation went wrong when the comment on the line above
      looked like a method call/member access:
      
          fn main() {
              // Lorem ipsum lorem ipsum lorem ipsum lorem.ipsum
                                                      foo.bar()
          }
      
      With this patch:
      
          fn main() {
              // Lorem ipsum lorem ipsum lorem ipsum lorem.ipsum
              foo.bar()
          }
      
      Also, a blank line or a comment broke method-chain indentation:
      
          fn main() {
              something.a.do_it
              // A comment
                  .aligned
      
                  .more_alignment();
          }
      
      With this patch:
      
          fn main() {
              something.a.do_it
              // A comment
                         .aligned
      
                         .more_alignment();
          }
      
      Note that comments interleaving a method chain are not aligned with the
      '.' of the method chain.
      fba77143
  8. 09 Sep, 2016 3 commits
  9. 20 Aug, 2016 1 commit
  10. 18 Aug, 2016 1 commit
  11. 15 Aug, 2016 1 commit
  12. 03 Aug, 2016 2 commits
    • Wilfred Hughes's avatar
      Go back to the current line and column after formatting. · 2540d7ef
      Wilfred Hughes authored
      The previous approach simply moved to the same character offset. This is
      unlikely to preserve the position of point, as rustfmt often changes
      whitespace, changing the number of characters before point.
      
      Instead, we go back to the line number and column number we were on
      before. Provided that rustfmt has not radically changed the number of
      lines, this will typically put point back to its previous position, or
      at least close.
      
      Improves, but doesn't completely solve, issue #162.
      2540d7ef
    • Wilfred Hughes's avatar
      rust--after-revert-hook should preserve point position. · e452995b
      Wilfred Hughes authored
      Otherwise, rust-format-buffer always moves point to the end of the
      buffer.
      e452995b
  13. 26 Jul, 2016 1 commit
  14. 22 Jul, 2016 3 commits
  15. 21 Jul, 2016 1 commit
  16. 20 Jul, 2016 1 commit
  17. 19 Jul, 2016 1 commit
    • Fanael Linithien's avatar
      Fix #160 · 620d7182
      Fanael Linithien authored
      Use `font-lock-fontify-region` on the whole buffer to actually force
      refontification in Emacs 24, which does not support `font-lock-ensure`.
      
      `font-lock-fontify-buffer` is actually closer to `font-lock-flush`, so it's not
      the right function to use in `rust--after-revert-hook`.
      620d7182
  18. 15 Jul, 2016 1 commit
  19. 17 May, 2016 1 commit
  20. 14 May, 2016 3 commits
    • fmdkdd's avatar
      Add menu titles for items in imenu · c69adaf8
      fmdkdd authored
      All items gathered by imenu were put at the top-level, except impls.
      
      This commit puts all items in separate menu titles, following "Impl".
      
      Fixes #93.
      c69adaf8
    • fmdkdd's avatar
      Add macro_rules names to imenu · e6eceea8
      fmdkdd authored
      imenu did not register macros previously.
      
      We must add `!` to the `word` syntax category for imenu since we reuse
      the `rust-re-item-def-imenu` regexp which use word boundaries.
      e6eceea8
    • fmdkdd's avatar
      imenu: don't add item defs in single-line comments · e3c545ec
      fmdkdd authored
      Fixes #94.
      
      This commit changes the regexp used to build
      `rust-imenu-generic-expression` to strictly match item definitions
      on lines that are not single-line comments.
      e3c545ec
  21. 06 May, 2016 1 commit
  22. 04 May, 2016 1 commit
    • Niko Matsakis's avatar
      add code to handle new-style rustc errors · 40c33fd7
      Niko Matsakis authored
      These errors are available on nightly builds (or will be soon), but
      only (at the moment) when enabled via environment variable. They will
      become the default at some point in the future.
      
      In this commit we match on the `-->`, but after that we have to scroll
      the compilation window to make the error visible. One shortcoming is
      that if you enter the window and click on the filename/line-number, then
      the "next-error-hook" doesn't seem to run. (If you click at the start of
      the line, it does.) It may be possible to tweak the "hyperlink" here to
      make that work more smoothly, or perhaps add a hook somewhere else.
      40c33fd7
  23. 26 Apr, 2016 1 commit
  24. 25 Apr, 2016 1 commit
    • mrBliss's avatar
      Properly fix #151 · eafb7a0f
      mrBliss authored
      Always check whether we're not in a string or comment when looking for
      the `where` keyword. Use two helpers for this: `rust-looking-at-where`
      and `rust-rewind-to-where`.
      eafb7a0f