tuckfoot

Fell-i

Talɣut ɣef uneflay
Isem tuckfoot
Adig New York
Axeddim Mastering Engineer
D aseqdac si Feb. 22, 2016
Amḍan n izegrar yuttusneflin 0 izegrar
Talemmast n tezmilin n izegrar n uneflay Ur yettwasezmel ara

Iceggiren-iw

Edit Email Subject (EES)

Yettwasezmel 4 ɣef 5 n yetran

Extremely useful and easy to use.

As others have noted, the renaming dialogue produces a spinner, then an "X" and seems to have failed. But, it hasn't actually failed. The renamed mail finally appears right next to the original version, which I then delete.

Unfortunately the above spinner+X process happens at every renaming, and takes between 10-15 seconds, during which nothing else can be done. A significant upgrade would reduce the wait to a second or two.

Thanks for a nice add-on and for listening.

Aseqdac-agi ɣur-s acegger yezrin n uzegrir-agi.

Edit Email Subject

Yettwasezmel 5 ɣef 5 n yetran

I am super happy to have this extension back again. Thanks to the new developer Dillinger!

Users report the ability to specify "local" or "server" changes. I would definitely opt for "server" but I cannot find such a preference (MacOS el capitan).

It would be great if someone could post the location of the switch.

I would make a contribution if a method were clear!

This review is for a previous version of the add-on (2.3). 

Edit Email Subject (EES)

Yettwasezmel 5 ɣef 5 n yetran

EditEmailSubject is simple and perfect. Or at least it was, before being disabled in TB68.

Like many other folks, I ask you to update this extension for TB68. The ability to modify Subjects seems so ordinary and necessary, that I'm insanely frustrated now that it's gone.

I'll also take this opportunity to apologize to the developer for not sending a contribution for your creation. I look forward to rectifying that situation as soon as it returns.

If I had known I was going to lose EES, I would have stayed in TB60.

This review is for a previous version of the add-on (2.1.1). 

Dropbox for Filelink (Broken)

Yettwasezmel 3 ɣef 5 n yetran

Took 5 tries, including removing and reactivating it, then establishing it within TB as a Filelink drive. (Many tries.)
So, thanks!