Date: prev next · Thread: first prev next last
2011 Archives by date, by thread · List index


On 13/09/2011, Michael Reich <reich.mikey@gmail.com> wrote:
The format of the LibreOffice digest mail list is driving me crazy.   It
doesn't seem to be threaded (grouping like messages together) at all and
it's a huge annoyance to lumber through the topics to see what's in the
digest.   The old OOO digest was/is much better organized.   Is there a
way for me to get my digest in a more organized format?


Viewing this digest via the gmail web interface, you should note that
all messages are viewed "inline" and not as attachments, which is the
standard expected behaviour stated by one of the LO programmers.
Messages seem to be organised via date. To reply to messages from
digest mode, the recommended method is to use the reply address
syntax: users+get-[messagenumber]@... to receive an individual message
of interest. This allows the thread to be maintained for specific
messages that you write replies, whilst the advantage of digest mode
(i.e. a single message) is retained separately.

-- 
For unsubscribe instructions e-mail to: users+help@global.libreoffice.org
Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/
Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette
List archive: http://listarchives.libreoffice.org/global/users/
All messages sent to this list will be publicly archived and cannot be deleted

Context


Privacy Policy | Impressum (Legal Info) | Copyright information: Unless otherwise specified, all text and images on this website are licensed under the Creative Commons Attribution-Share Alike 3.0 License. This does not include the source code of LibreOffice, which is licensed under the Mozilla Public License (MPLv2). "LibreOffice" and "The Document Foundation" are registered trademarks of their corresponding registered owners or are in actual use as trademarks in one or more countries. Their respective logos and icons are also subject to international copyright laws. Use thereof is explained in our trademark policy.