Custom Query (332 matches)

Filters
 
Or
 
  
 
Columns

Show under each result:


Results (58 - 60 of 332)

Ticket Resolution Summary Owner Reporter
#260 invalid Test2 with new database inplace bas bas.van.der.vlies@…
Description
lets see
#12 wontfix email2trac installation problem bas bb.bek69@…
Description

Hi, following the guide, i did: ./configure --prefix=/home/.../.../ make make install

but at step "make install":

if [ ! -f home/...etc/email2trac.conf ] ; \ then \

./install-sh -c -m 644 -o root email2trac.conf home/...etc/email2trac.conf ;\

fi chown: changing ownership of `home/...etc/#inst.14834#': Operation not permitted make: * [install-conf] Error 1

Can anybody help me?

#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

  • 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

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]:

reflow: 1 OPTIONAL, if set then soft line breaks will be removed from [format:flowed] email when creating the ticket with verbatim_format turned off
Note: See TracQuery for help on using queries.