Permalink
Commits on Feb 29, 2012
  1. Use lib_dirs from Rebar also in the compiler escript

    jimenezrick committed Feb 29, 2012
    Useful if using some custom behaviour code in your lib_dirs.
  2. Improve omni completion escript

    jimenezrick committed Feb 29, 2012
    Use code:add_path[s]a/1 and reorder code path additions like this:
    
    ebin > deps > lib_dirs > OTP
  3. Improve compiler escript

    jimenezrick committed Feb 29, 2012
    Use code:add_path[s]a/1 to give priority to the code from the user. Also
    add to code path ebin/, useful for custom behaviours, as the compiler
    need to check with the callbacks.
  4. Add lib_dirs to omni completed paths

    Ignas Vyšniauskas committed Feb 29, 2012
Commits on Feb 28, 2012
  1. Merge pull request #20 from choptastic/include_depth

    jimenezrick committed Feb 28, 2012
    Fix to search deeper to find include files
  2. Improve behaviour skeletons

    jimenezrick committed Feb 28, 2012
  3. Close #19: fix escript not working on OS X 10.7

    jimenezrick committed Feb 28, 2012
    Now the indenter escript is started in a detached VM becasuse with
    MacVim it is started without a TTY/PTY attach.
Commits on Feb 24, 2012
  1. Don't define DEBUG and TEST macros on syntax check

    jimenezrick committed Feb 24, 2012
    Let the user define these macros if he wants to.
Commits on Feb 18, 2012
  1. Add more test code

    Ricardo committed Feb 18, 2012
  2. Add a separate indenting test for spaces and tabs

    Ricardo committed Feb 18, 2012
  3. Update tests

    Ricardo committed Feb 18, 2012
  4. Improve -export indenting using tabs

    Ricardo committed Feb 18, 2012
  5. Improve tests

    jimenezrick committed Feb 18, 2012
Commits on Feb 17, 2012
Commits on Feb 15, 2012
  1. Remove empty lines

    jimenezrick committed Feb 15, 2012
Commits on Feb 8, 2012
Commits on Feb 6, 2012
Commits on Feb 5, 2012
  1. Catch when EDoc exits on error

    jimenezrick committed Feb 5, 2012
    This happens when EDoc tries to analyze a module where the spec
    declarations are not exactly above the functions they describe. This is
    an example with the module `ssl' which causes these kind of troubles:
    
    ---8<-- ssl.erl ------------------------------------------------------------------
    -spec start() -> ok  | {error, reason()}.
    -spec start(permanent | transient | temporary) -> ok | {error, reason()}.
    start() ->
        application:start(crypto),
        application:start(public_key),
        application:start(ssl).
    
    start(Type) ->
        application:start(crypto, Type),
        application:start(public_key, Type),
        application:start(ssl, Type).
    ---8<--------------------------------------------------------------------
    
    With this solution, an error is shown, but at least the module_info/1
    function is used to give the rest of the module's exported functions.
  2. Fix errorformat

    jimenezrick committed Feb 5, 2012
    Not handling multi-line errors/warnings, necessary? :-/
Commits on Feb 4, 2012
Commits on Feb 3, 2012
Commits on Feb 2, 2012
  1. Add TODO

    jimenezrick committed Feb 2, 2012
Commits on Jan 31, 2012
  1. Update doc

    jimenezrick committed Jan 31, 2012
Commits on Jan 30, 2012
  1. Convert syntax file to UTF-8

    jimenezrick committed Jan 30, 2012
Commits on Jan 29, 2012
  1. Update doc

    jimenezrick committed Jan 29, 2012