no output from sassc when using output mode different from nested

[FelixSchwarz]

I don't get any output from sassc if I use the '-t' option with a value different from 'nested'.

For example:

$ sassc -t expanded test.sass
# no output at all

My test.sass file is pretty simple:

$color: #eeeeee;

body {
  font: {
    color: $color;
  }
}

I'm using libsass 9c05850 and sassc 4905e0e (afaik the latest versions as of March 20 2013) on Fedora 18 with a shared libsass.

[craigbarnes]

sassc just interprets the options and passes them to libsass, which currently only supports nested and compressed. I guess the bug is that both sassc and libsass ignore the unimplemented options silently.

[FelixSchwarz]

Also I'd say it's a problem that the help text of sassc mentions them.

May I assume you also file an issue for libsass if necessary or should I add a new ticket there as well.

[craigbarnes]

May I assume you also file an issue for libsass if necessary or should I add a new ticket there as well.

I'm not libsass developer, I just thought I'd do some drive-by support here, since the developers seem tied down with other things ;)

I guess libsass would be the right place to report it, yes.

[akhleung]

Sorry, I've been busy with other things. I believe this issue has already been filed in the LibSass repo.

[FelixSchwarz]

ah, right this seems to be issue 15 (sass/libsass#15).

But as at least some modes are non-functional at the moment maybe you should only list/accept working options in sassc?

[akhleung]

Oh, yeah, libsass just spits out empty strings for unsupported output formats. I suppose we can make it emit a warning.

[HamptonMakes]

We'll add support to the libsass ticket.

[HamptonMakes]

Ahem. What I mean to say is, that when support for the other formats comes out, we'll update sassc, but until then, the issue is really with libsass. So, now that the sassc --help options have been fixed, sassc is in compliance and so this ticket can be closed.