Custom Query (332 matches)
Results (70 - 72 of 332)
| Ticket | Resolution | Summary | Owner | Reporter | |||
|---|---|---|---|---|---|---|---|
| #91 | fixed | Config file parsing issue | bas | Matthew.Carlson@… | |||
| Description |
Email2trac doesn't work with [DEFAULT] configuration. Fails with the message "No Trac project is defined in the email2trac config file." If I use the named project configuration (Ex: [bas]), and then call email2trac with the --project bas option it works fine. Maybe something changed in the config-parsing dependencies? Environment: Windows XP Python 2.5 Trac 0.11.1 Email2Trac 0.30 |
||||||
| #92 | fixed | Possible to give examples of usage on the wiki? | anonymous | anonymous | |||
| Description |
This sounds fantastic, but I am having trouble understanding what a user actually sends in their email when using email2trac. Is it possible to add some examples of usage, for a recommended workflow/configuration? E.g. show the emails to:
|
||||||
| #94 | fixed | Support for RFC 3676 (format=flowed) | bas | ben@… | |||
| Description |
Most email clients wrap long lines to <80 characters. In some cases, this breaks Trac wiki formatting (when verbatim_format is off). For example: * This is a very very very very very very very very very very very very very very very very very very very very very very very very very very very very very very very very long list item may get incorrectly rendered as
very very very very very very very very very very very very very very very very very very very very long list item Format=flowed property of plain-text email, specified in RFC 3676, deals with this problem. The attached patch (against email2trac 0.5) implements format=flowed support. When this patch is applied, the following should be added to [wiki/Email2tracConfiguration]:
|
||||||
