My favorites | Sign in
Project Logo
             
Details: Show all Hide all

Last 7 days

Older

  • Nov 27, 2009
    erlware-mode-0.1.18.zip (Erlware mode release zip.) file uploaded by dave.peticolas   -  
    Labels: Featured Type-Source OpSys-All
    Labels: Featured Type-Source OpSys-All
  • Nov 27, 2009
    erlware-mode-0.1.18.tar.gz (Erlware mode release tar file.) file uploaded by dave.peticolas   -  
    Labels: Featured Type-Source OpSys-All
    Labels: Featured Type-Source OpSys-All
  • Oct 11, 2009
    erlware-mode-0.1.17.zip (Erlware mode release zip.) file uploaded by dave.peticolas   -  
    Labels: Featured Type-Source OpSys-All
    Labels: Featured Type-Source OpSys-All
  • Oct 11, 2009
    erlware-mode-0.1.17.tar.gz (Erlware mode release tar file.) file uploaded by dave.peticolas   -  
    Labels: Featured Type-Source OpSys-All
    Labels: Featured Type-Source OpSys-All
  • Aug 09, 2009
    erlware-mode-0.1.16.zip (Erlware mode release zip.) file uploaded by dave.peticolas   -  
    Labels: Featured Type-Source OpSys-All
    Labels: Featured Type-Source OpSys-All
  • Aug 09, 2009
    erlware-mode-0.1.16.tar.gz (Erlware mode release tar file.) file uploaded by dave.peticolas   -  
    Labels: Featured Type-Source OpSys-All
    Labels: Featured Type-Source OpSys-All
  • Jul 09, 2009
    issue 37 (Indentation rules ignores that no tab chars should be used) Status changed by dave.peticolas   -   Cool, no problem!
    Status: Invalid
    Cool, no problem!
    Status: Invalid
  • Jul 09, 2009
    issue 37 (Indentation rules ignores that no tab chars should be used) commented on by magnus.falk   -   After some fiddling it seems to work. Thanks a lot! This've been bugging me for ages!
    After some fiddling it seems to work. Thanks a lot! This've been bugging me for ages!
  • Jul 08, 2009
    issue 37 (Indentation rules ignores that no tab chars should be used) commented on by dave.peticolas   -   I'm no Emacs expert either, but try changing your file like this: (custom-set-variables '(font-lock-maximum-decorations t) '(global-font-lock-mode t) '(c-basic-offset 4) ... etc. ) Instead of using 'setq'. dave
    I'm no Emacs expert either, but try changing your file like this: (custom-set-variables '(font-lock-maximum-decorations t) '(global-font-lock-mode t) '(c-basic-offset 4) ... etc. ) Instead of using 'setq'. dave
  • Jul 08, 2009
    issue 37 (Indentation rules ignores that no tab chars should be used) commented on by magnus.falk   -   I tried your suggestion and yes, it works if I use indent-level 2, but as soon as the indentation is to be an even 8 spaces emacs will put a tab there instead. Try it with indent-level set to 4 and you'll probably see it. My .emacs (mind you, I know next to nothing about emacs): (setq load-path (cons "/home/efalmag/erlware-mode-0.1.15" load-path)) (setq erlang-root-dir "/vobs/otp/otp_delivery/solaris8_sparc") (setq exec-path (append '("/vobs/otp/otp_delivery/solaris8_sparc/bin") exec-path)) (require 'erlang-start) ;; Syntax highlightning (setq font-lock-maximum-decorations t) (global-font-lock-mode t) (setq c-basic-offset 4) (setq tab-width 2) (setq indent-tabs-mode nil) (setq erlang-indent-level 4) Cheers, Magnus
    I tried your suggestion and yes, it works if I use indent-level 2, but as soon as the indentation is to be an even 8 spaces emacs will put a tab there instead. Try it with indent-level set to 4 and you'll probably see it. My .emacs (mind you, I know next to nothing about emacs): (setq load-path (cons "/home/efalmag/erlware-mode-0.1.15" load-path)) (setq erlang-root-dir "/vobs/otp/otp_delivery/solaris8_sparc") (setq exec-path (append '("/vobs/otp/otp_delivery/solaris8_sparc/bin") exec-path)) (require 'erlang-start) ;; Syntax highlightning (setq font-lock-maximum-decorations t) (global-font-lock-mode t) (setq c-basic-offset 4) (setq tab-width 2) (setq indent-tabs-mode nil) (setq erlang-indent-level 4) Cheers, Magnus
  • Jul 07, 2009
    issue 37 (Indentation rules ignores that no tab chars should be used) commented on by dave.peticolas   -   I can't reproduce this, I get spaces. To change the mode's indentation level, you will want to set erlang-indent-level to 2. Can you send your .emacs settings? dave
    I can't reproduce this, I get spaces. To change the mode's indentation level, you will want to set erlang-indent-level to 2. Can you send your .emacs settings? dave
  • Jul 07, 2009
    issue 36 (Indentation broken ) commented on by dave.peticolas   -   So you are saying that the indentation of the case is a bug? Why? I'd rather see it indented.
    So you are saying that the indentation of the case is a bug? Why? I'd rather see it indented.
  • Jul 07, 2009
    issue 35 (bad indentation for try-after expressions) Status changed by dave.peticolas   -   I believe this is unrelated to the tab indentation, but I will look into the tab problem. In the meantime, I think try/after indentation is actually fixed in 0.1.15.
    Status: Fixed
    I believe this is unrelated to the tab indentation, but I will look into the tab problem. In the meantime, I think try/after indentation is actually fixed in 0.1.15.
    Status: Fixed
  • Jul 07, 2009
    issue 35 (bad indentation for try-after expressions) commented on by magnus.falk   -   This looks related to my issue (#37), since the indentation seems to be using tab chars.
    This looks related to my issue (#37), since the indentation seems to be using tab chars.
  • Jul 07, 2009
    issue 37 (Indentation rules ignores that no tab chars should be used) reported by magnus.falk   -   What steps will reproduce the problem? 1. Write the first row of a case statement 2. press enter for newline 3. the case clause on the next line is indented with a tab char that is 8 spaces wide What is the expected output? What do you see instead? I have (setq indent-tabs-mode nil) and (setq tab-width 2) in my .emacs and would like to get the indentation in spaces instead of tabs. This is likely a problem in the original erlang mode since it's been bugging me for ages (I'm really a Vim user and the Vim mode does this correctly so all the source files look different in Vim). What version of the product are you using? On what operating system? erlware-mode-0.1.15 in Emacs 21.1 on Solaris 5.9 or Linux 2.6.16.46-0.12- bigsmp Please provide any additional information below.
    What steps will reproduce the problem? 1. Write the first row of a case statement 2. press enter for newline 3. the case clause on the next line is indented with a tab char that is 8 spaces wide What is the expected output? What do you see instead? I have (setq indent-tabs-mode nil) and (setq tab-width 2) in my .emacs and would like to get the indentation in spaces instead of tabs. This is likely a problem in the original erlang mode since it's been bugging me for ages (I'm really a Vim user and the Vim mode does this correctly so all the source files look different in Vim). What version of the product are you using? On what operating system? erlware-mode-0.1.15 in Emacs 21.1 on Solaris 5.9 or Linux 2.6.16.46-0.12- bigsmp Please provide any additional information below.
  • Jul 04, 2009
    erlware-mode-0.1.15.zip (Erlware mode release zip.) file uploaded by dave.peticolas   -  
    Labels: Featured Type-Source OpSys-All
    Labels: Featured Type-Source OpSys-All
  • Jul 04, 2009
    erlware-mode-0.1.15.tar.gz (Erlware mode release tar file.) file uploaded by dave.peticolas   -  
    Labels: Featured Type-Source OpSys-All
    Labels: Featured Type-Source OpSys-All
  • Jun 21, 2009
    issue 36 (Indentation broken ) reported by martinjlogan   -   What steps will reproduce the problem? Result = case RawArgString of ... end, What is the expected output? What do you see instead? Result = case RawArgString of ... end,
    What steps will reproduce the problem? Result = case RawArgString of ... end, What is the expected output? What do you see instead? Result = case RawArgString of ... end,
  • Jun 17, 2009
    issue 35 (bad indentation for try-after expressions) reported by samuelrivas   -   What steps will reproduce the problem? 1. write a try expression with an after section 2. 3. What is the expected output? What do you see instead? I get make_dir(Dir, Options) -> {ok, Old} = file:get_cwd(), try ok = file:set_cwd(Dir), make(Options) after file:set_cwd(Old) end. I expect something like: make_dir(Dir, Options) -> {ok, Old} = file:get_cwd(), try ok = file:set_cwd(Dir), make(Options) after file:set_cwd(Old) end. What version of the product are you using? On what operating system? 0.1.14 Please provide any additional information below.
    What steps will reproduce the problem? 1. write a try expression with an after section 2. 3. What is the expected output? What do you see instead? I get make_dir(Dir, Options) -> {ok, Old} = file:get_cwd(), try ok = file:set_cwd(Dir), make(Options) after file:set_cwd(Old) end. I expect something like: make_dir(Dir, Options) -> {ok, Old} = file:get_cwd(), try ok = file:set_cwd(Dir), make(Options) after file:set_cwd(Old) end. What version of the product are you using? On what operating system? 0.1.14 Please provide any additional information below.
  • Jun 05, 2009
    issue 34 (Functions with binaries and quotation marks don't indent cor...) reported by eproxus   -   What steps will reproduce the problem? 1. Create a function clause: func(<<$">>) -> 2. Try to indent the body. What is the expected output? What do you see instead? Expected: Body is indented correctly. Actual: Body is not indented at all. What version of the product are you using? On what operating system? erlware-mode-0.1.14 Emacs 22.2.1 SuSE SLED Linux 10 SP1 Please provide any additional information below. Seems to be valid for all functions which have binary clauses with dollar and a quotation sign (") in them.
    What steps will reproduce the problem? 1. Create a function clause: func(<<$">>) -> 2. Try to indent the body. What is the expected output? What do you see instead? Expected: Body is indented correctly. Actual: Body is not indented at all. What version of the product are you using? On what operating system? erlware-mode-0.1.14 Emacs 22.2.1 SuSE SLED Linux 10 SP1 Please provide any additional information below. Seems to be valid for all functions which have binary clauses with dollar and a quotation sign (") in them.
  • May 20, 2009
    erlware-mode-0.1.14.zip (Erlware mode release zip.) file uploaded by dave.peticolas   -  
    Labels: Featured Type-Source OpSys-All
    Labels: Featured Type-Source OpSys-All
  • May 20, 2009
    erlware-mode-0.1.14.tar.gz (Erlware mode release tar file.) file uploaded by dave.peticolas   -  
    Labels: Featured Type-Source OpSys-All
    Labels: Featured Type-Source OpSys-All
  • May 15, 2009
    erlware-mode-0.1.13.zip (Erlware mode release zip.) file uploaded by dave.peticolas   -  
    Labels: Featured Type-Source OpSys-All
    Labels: Featured Type-Source OpSys-All
  • May 15, 2009
    erlware-mode-0.1.13.tar.gz (Erlware mode release tar file.) file uploaded by dave.peticolas   -  
    Labels: Featured Type-Source OpSys-All
    Labels: Featured Type-Source OpSys-All
  • May 12, 2009
    issue 33 ('++' highlighted incorrectly) reported by eproxus   -   What steps will reproduce the problem? 1. Type '++' in an Erlang file. 2. Watch color. What is the expected output? What do you see instead? Expected: the plusses highlighted with the atom color. Actual: the plusses highlighted with the operator color. What version of the product are you using? On what operating system? erlware-mode-0.1.12, XEmacs 21.5.25 of February 2006 (+CVS-20060326), SuSE SLED Linux 10 SP1
    What steps will reproduce the problem? 1. Type '++' in an Erlang file. 2. Watch color. What is the expected output? What do you see instead? Expected: the plusses highlighted with the atom color. Actual: the plusses highlighted with the operator color. What version of the product are you using? On what operating system? erlware-mode-0.1.12, XEmacs 21.5.25 of February 2006 (+CVS-20060326), SuSE SLED Linux 10 SP1
  • May 05, 2009
    erlware-mode-0.1.12.zip (Erlware mode release zip.) file uploaded by dave.peticolas   -  
    Labels: Featured Type-Source OpSys-All
    Labels: Featured Type-Source OpSys-All
  • May 05, 2009
    erlware-mode-0.1.12.tar.gz (Erlware mode release tar file.) file uploaded by dave.peticolas   -  
    Labels: Featured Type-Source OpSys-All
    Labels: Featured Type-Source OpSys-All
  • Mar 21, 2009
    issue 27 (Dollar at end of string triggers character syntax) commented on by dave.peticolas   -   Still not fixed, but the work-around with 0.1.11 is to end the string like this: \$" It functionally equivalent and will highlight correctly.
    Still not fixed, but the work-around with 0.1.11 is to end the string like this: \$" It functionally equivalent and will highlight correctly.
  • Mar 21, 2009
    issue 31 (syntax highlighting issue) Status changed by dave.peticolas   -  
    Status: Fixed
    Status: Fixed
  • Mar 21, 2009
    erlware-mode-0.1.11.zip (Erlware mode release zip.) file uploaded by dave.peticolas   -  
    Labels: Featured Type-Source OpSys-All
    Labels: Featured Type-Source OpSys-All
  • Mar 21, 2009
    erlware-mode-0.1.11.tar.gz (Erlware mode release tar file.) file uploaded by dave.peticolas   -  
    Labels: Featured Type-Source OpSys-All
    Labels: Featured Type-Source OpSys-All
  • Mar 20, 2009
    issue 32 (naming in github is off) Status changed by dave.peticolas   -  
    Status: Fixed
    Status: Fixed
  • Mar 12, 2009
    issue 32 (naming in github is off) reported by martinjlogan   -   The erlware repo for this project is erlware-emacs-mode - should it not be erlware-mode. Why the new name?
    The erlware repo for this project is erlware-emacs-mode - should it not be erlware-mode. Why the new name?
  • Mar 12, 2009
    issue 31 (syntax highlighting issue) reported by martinjlogan   -   AppName = atom_to_list(element(1, AppSpec)), in that string currently atom_to_list is blue and element is green on my terminal. They are both bifs and should be the same color. For some reason element is highlighted as a non bif function.
    AppName = atom_to_list(element(1, AppSpec)), in that string currently atom_to_list is blue and element is green on my terminal. They are both bifs and should be the same color. For some reason element is highlighted as a non bif function.
  • Feb 18, 2009
    issue 30 (Syntax highlighting error with dynamic function call names) Status changed by dave.peticolas   -   So Mats fixed this by making the variables highlight as variables.
    Status: Fixed
    So Mats fixed this by making the variables highlight as variables.
    Status: Fixed
  • Feb 18, 2009
    erlware-mode-0.1.10.zip (Erlware mode release zip.) file uploaded by dave.peticolas   -  
    Labels: Featured Type-Source OpSys-All
    Labels: Featured Type-Source OpSys-All
  • Feb 18, 2009
    erlware-mode-0.1.10.tar.gz (Erlware mode release tar file.) file uploaded by dave.peticolas   -  
    Labels: Featured Type-Source OpSys-All
    Labels: Featured Type-Source OpSys-All
  • Feb 17, 2009
    issue 30 (Syntax highlighting error with dynamic function call names) Summary changed by martinjlogan   -  
    Summary: Syntax highlighting error with dynamic function call names
    Summary: Syntax highlighting error with dynamic function call names
  • Feb 17, 2009
    issue 30 (Syntax highlighting error ) reported by martinjlogan   -   Just pulled the latest version and noticed a syntax highlighting error. Module:some_func(Arg) In this scheme the odule:some_func( part will be one color, the correct color for function calls but the "M" is black.
    Just pulled the latest version and noticed a syntax highlighting error. Module:some_func(Arg) In this scheme the odule:some_func( part will be one color, the correct color for function calls but the "M" is black.
  • Feb 16, 2009
    erlware-mode-0.1.9.zip (Erlware mode release zip.) file uploaded by dave.peticolas   -  
    Labels: Featured Type-Source OpSys-All
    Labels: Featured Type-Source OpSys-All
  • Feb 16, 2009
    erlware-mode-0.1.9.tar.gz (Erlware mode release tar file.) file uploaded by dave.peticolas   -  
    Labels: Featured Type-Source OpSys-All
    Labels: Featured Type-Source OpSys-All
  • Jan 23, 2009
    issue 28 (bad indentation on ${) Status changed by dave.peticolas   -  
    Status: Accepted
    Status: Accepted
  • Jan 20, 2009
    issue 28 (bad indentation on ${) reported by martinjlogan   -   transform_term(Term, [${|T]) -> results in incorrect indentation because the mode thinks that there is an open tuple that it needs to account form.
    transform_term(Term, [${|T]) -> results in incorrect indentation because the mode thinks that there is an open tuple that it needs to account form.
  • Dec 11, 2008
    issue 27 (Dollar at end of string triggers character syntax) changed by dave.peticolas   -  
    Status: Accepted
    Labels: Type-Defect
    Status: Accepted
    Labels: Type-Defect
  • Dec 11, 2008
    issue 25 (False positives in builtin highlighting) Status changed by dave.peticolas   -  
    Status: Fixed
    Status: Fixed
  • Dec 11, 2008
    erlware-mode-0.1.8.zip (Erlware mode release zip.) file uploaded by dave.peticolas   -  
    Labels: Featured Type-Source OpSys-All
    Labels: Featured Type-Source OpSys-All
  • Dec 11, 2008
    erlware-mode-0.1.8.tar.gz (Erlware mode release tar file.) file uploaded by dave.peticolas   -  
    Labels: Featured Type-Source OpSys-All
    Labels: Featured Type-Source OpSys-All
  • Nov 05, 2008
    issue 27 (Dollar at end of string triggers character syntax) reported by eproxus   -   What steps will reproduce the problem? 1. Enter the string "$" 2. Write code after the string What is the expected output? What do you see instead? Expected: Normal syntax high lighting. Actual: String-colored syntax high lighting. What version of the product are you using? On what operating system? erlware-mode-0.1.6 & Xemacs 21.5.25 of February 2006 (+CVS-20060326) on SuSE 10.2.
    What steps will reproduce the problem? 1. Enter the string "$" 2. Write code after the string What is the expected output? What do you see instead? Expected: Normal syntax high lighting. Actual: String-colored syntax high lighting. What version of the product are you using? On what operating system? erlware-mode-0.1.6 & Xemacs 21.5.25 of February 2006 (+CVS-20060326) on SuSE 10.2.
 
Hosted by Google Code