You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@openoffice.apache.org by Srinivasulu Bhattaram <bh...@gmail.com> on 2012/06/27 23:53:11 UTC
Space before every line
I have a text file, which has one space before every line
How to remove this using search and replace option
For carriage return or <Enter>, I learnt that we hould use "\n" (quotes not
included) and keep Regular Expressions on.
But I do not know what is code for space
Can nay one let me know?
seena
---------------------------------------------------------------------
To unsubscribe, e-mail: ooo-users-unsubscribe@incubator.apache.org
For additional commands, e-mail: ooo-users-help@incubator.apache.org
Re: Space before every line
Posted by Niall Martin <ni...@rndmartin.cix.co.uk>.
I like the look of this too.
On 28 Jun 2012 at 17:55, Rory O'Farrell wrote:
Send reply to: ooo-users@incubator.apache.org
Date sent: Thu, 28 Jun 2012 17:55:18 +0100
From: "Rory O'Farrell" <of...@iol.ie>
To: ooo-users@incubator.apache.org
Subject: Re: Space before every line
> Perhaps a valid solution might be a rewrite of Find and Replace,
> simplifying it and allowing it to use various tokens so that Regular
> Expression usage was completely concealed or even disabled.
>
> Then add (if permitted by the author) AltSearch,
> http://extensions.services.openoffice.org/en/search/node/altsearch or
> advise its download as an extension; this is a much more powerful
> mechanism and which could be available but out of the way of the
> inexperienced User.
Niall Martin
Phone 0131 4678468
Please reply to: niall<at>rndmartin.cix.co.uk
---------------------------------------------------------------------
To unsubscribe, e-mail: ooo-users-unsubscribe@incubator.apache.org
For additional commands, e-mail: ooo-users-help@incubator.apache.org
Re: Space before every line
Posted by Rob Weir <ro...@apache.org>.
On Thu, Jun 28, 2012 at 12:45 PM, Armin Le Grand <Ar...@me.com> wrote:
> Rob Weir <ro...@apache.org> wrote:
>> On Thu, Jun 28, 2012 at 6:57 AM, Armin Le Grand <Ar...@me.com> wrote:
>>> Hi Kevin,
>>>
>>> Kevin Grignon <ke...@gmail.com> wrote:
>>>> KG01-see comments inline.
>>>>
>>>> On Thursday, June 28, 2012, Dan wrote:
>>>>
>>>>> Srinivasulu Bhattaram wrote:
>>>>>
>>>>>> I have a text file, which has one space before every line
>>>>>> How to remove this using search and replace option
>>>>>> For carriage return or <Enter>, I learnt that we hould use "\n" (quotes
>>>>>> not included) and keep Regular Expressions on.
>>>>>> But I do not know what is code for space
>>>>>
>>>>>
>>>> KG01 - Why is this so complicated. Such system language hides the power of
>>>> the tool. The tool should understand natural language inputs.
>>>
>>> I already thought the same. Regular expressions are mighty, but only
>>> (guessed) 5% of the users understand it (as with many mighty things). My
>>> first idea was to add buttons which add the 'coded' entries tothe
>>> expression, e.g.: Button 'Space' adds '\n' when pressed to the text field.
>>> Same for 'Start of Line' adding '^'. Much more to be defined, may someone
>>> knowing regular expressions well list more of them.
>>> Another way would be to allow tokens like <Space> which get translated to
>>> '\n' internally before using the expression, but then the user would again
>>> have to remember multiple tokens and how they are spelled (need to be
>>> valid, possible errors which need to be handled).
>>> Maybe a mix of both, press button 'Space' adds the (human readable) token
>>> <Space> which itself is not editable (represents a single character).
>>> Hmmm...
>>>
>>
>> Have you seen what the SlickEdit coding editor has? Here is their
>> search dialog:
>>
>> http://people.apache.org/~robweir/slickedit-re-dialog.png
>>
>> So you can click a button to pop out a list of common RE patterns.
>
> Interesting. What is inserted into the text field, then? Some
> human-readable tokens, or the RE ones?
>
It inserts the RE codes. So you would still need to know some RE
syntax to work with groups, etc.
The other approach -- and I think this is theoretically possible --
is to have the user define a search pattern by example and counter
example. But this might be too slow.
Even among programmers RE knowledge is imperfect and they sometimes
operate in unexpected ways. So even some sort of live preview could
help, e.g., a window that shows the kind of things that will be
matched before you run your search and replace operation.
-Rob
>> But this is more of an aid to someone who already understands RE's.
>> I'm not sure we can do much to make this conceptually much easier for
>> end users, since regular expressions have a certain amount of
>> essential complexity. Or would it make sense to support more than one
>> RE variation, maybe full RE, but also DOS-style with only * and ?
>> qualifiers?
>
> That is what MSDEV (Developer studio) does. It allows to choose between
> 'Wildcarts' and 'Regular expression', where the first one accepts simple
> '*' placeholders. An alternative for users, but limited. Maybe a good
> compromize...
>
>> -Rob
>>
>>
>>>> Perhaps we could explore ways to provide such system-oriented syntax to the
>>>> user in the context of the task. In other words, update the UI design to
>>>> include a way to evoke a cheat sheet, or even better, implement a way for
>>>> the user to insert syntax using natural language, with the system
>>>> interpreting behind the scenes.
>>>>
>>>> I suppose this is a broader usability theme that appears throughout the
>>>> toolset. We should explore ways reduce the complexity of system-oriented
>>>> command inputs and make advanced capabilities more consumable to less
>>>> technical users.
>>>>
>>>> After all, this is a tool to help people capture their thoughts and share
>>>> ideas - not a development environment.
>>>>
>>>> Thoughts?
>>>>
>>>>> Can any one let me know?
>>>>>> seena
>>>>>
>>>>>
>>>>> If you are using a carriage return (shift+<Enter>) or <Enter>, you can
>>>>> use this: "^ " (^ followed by a space). Regular Expressions must be on.
>>>>> The replace box should be empty.
>>>>> Search and replace as you did using "\n" above.
>>>>>
>>>>> --Dan
>>>>>
>>>>> ------------------------------**------------------------------**---------
>>>>> To unsubscribe, e-mail: ooo-users-unsubscribe@incubator.apache.org
>>>>> For additional commands, e-mail: ooo-users-help@incubator.apache.org
>>>>>
>>>>>
>>>
>>>
>>> --
>>> ALG
>>>
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: ooo-users-unsubscribe@incubator.apache.org
>>> For additional commands, e-mail: ooo-users-help@incubator.apache.org
>>>
>
>
> --
> ALG
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: ooo-users-unsubscribe@incubator.apache.org
> For additional commands, e-mail: ooo-users-help@incubator.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: ooo-users-unsubscribe@incubator.apache.org
For additional commands, e-mail: ooo-users-help@incubator.apache.org
Re: Space before every line
Posted by Johnny Rosenberg <gu...@gmail.com>.
2012/6/28 Armin Le Grand <Ar...@me.com>:
> Rob Weir <ro...@apache.org> wrote:
>> On Thu, Jun 28, 2012 at 6:57 AM, Armin Le Grand <Ar...@me.com> wrote:
>>> Hi Kevin,
>>>
>>> Kevin Grignon <ke...@gmail.com> wrote:
>>>> KG01-see comments inline.
>>>>
>>>> On Thursday, June 28, 2012, Dan wrote:
>>>>
>>>>> Srinivasulu Bhattaram wrote:
>>>>>
>>>>>> I have a text file, which has one space before every line
>>>>>> How to remove this using search and replace option
>>>>>> For carriage return or <Enter>, I learnt that we hould use "\n" (quotes
>>>>>> not included) and keep Regular Expressions on.
>>>>>> But I do not know what is code for space
>>>>>
>>>>>
>>>> KG01 - Why is this so complicated. Such system language hides the power of
>>>> the tool. The tool should understand natural language inputs.
>>>
>>> I already thought the same. Regular expressions are mighty, but only
>>> (guessed) 5% of the users understand it (as with many mighty things). My
>>> first idea was to add buttons which add the 'coded' entries tothe
>>> expression, e.g.: Button 'Space' adds '\n' when pressed to the text field.
>>> Same for 'Start of Line' adding '^'. Much more to be defined, may someone
>>> knowing regular expressions well list more of them.
>>> Another way would be to allow tokens like <Space> which get translated to
>>> '\n' internally before using the expression, but then the user would again
>>> have to remember multiple tokens and how they are spelled (need to be
>>> valid, possible errors which need to be handled).
>>> Maybe a mix of both, press button 'Space' adds the (human readable) token
>>> <Space> which itself is not editable (represents a single character).
>>> Hmmm...
>>>
>>
>> Have you seen what the SlickEdit coding editor has? Here is their
>> search dialog:
>>
>> http://people.apache.org/~robweir/slickedit-re-dialog.png
>>
>> So you can click a button to pop out a list of common RE patterns.
>
> Interesting. What is inserted into the text field, then? Some
> human-readable tokens, or the RE ones?
>
>> But this is more of an aid to someone who already understands RE's.
>> I'm not sure we can do much to make this conceptually much easier for
>> end users, since regular expressions have a certain amount of
>> essential complexity. Or would it make sense to support more than one
>> RE variation, maybe full RE, but also DOS-style with only * and ?
>> qualifiers?
>
> That is what MSDEV (Developer studio) does. It allows to choose between
> 'Wildcarts' and 'Regular expression', where the first one accepts simple
> '*' placeholders. An alternative for users, but limited. Maybe a good
> compromize...
>
>> -Rob
If you have two choices and you pick both, it's not a compromise, is it?
Kind regards
Johnny Rosenberg
ジョニー・ローゼンバーグ
---------------------------------------------------------------------
To unsubscribe, e-mail: ooo-users-unsubscribe@incubator.apache.org
For additional commands, e-mail: ooo-users-help@incubator.apache.org
Re: Space before every line
Posted by Kevin Grignon <ke...@gmail.com>.
KG02 - See comments inline
On Fri, Jun 29, 2012 at 9:05 AM, Guenter Marxen <
guenter.marxen@googlemail.com> wrote:
> Hello,
>
> if I recall correctly, there is only spoken of space before (or perhaps
> after) a "text line" in Writer.
>
> There are paragraph attributes in (german) "Einzüge und Abstände" (perhaps
> in English 'Indents and Distances") "Abstand Über" or "Unter Absatz" (Engl.
> perhaps Distence above / under) and "Zeilenabstand" (perhaps "line
> distance").
>
> Perhaps you control the parapraph attributes?
>
> MfG
> G. Marxen
>
> Am 28.06.2012 18:55, schrieb Rory O'Farrell:
>
> On Thu, 28 Jun 2012 16:45:54 +0000 (UTC)
>> Armin Le Grand <Ar...@me.com> wrote:
>>
>> Rob Weir <ro...@apache.org> wrote:
>>>
>>>> On Thu, Jun 28, 2012 at 6:57 AM, Armin Le Grand <Ar...@me.com>
>>>> wrote:
>>>>
>>>>> Hi Kevin,
>>>>>
>>>>> Kevin Grignon <ke...@gmail.com> wrote:
>>>>>
>>>>>> KG01-see comments inline.
>>>>>>
>>>>>> On Thursday, June 28, 2012, Dan wrote:
>>>>>>
>>>>>> Srinivasulu Bhattaram wrote:
>>>>>>>
>>>>>>> I have a text file, which has one space before every line
>>>>>>>> How to remove this using search and replace option
>>>>>>>> For carriage return or <Enter>, I learnt that we hould use "\n"
>>>>>>>> (quotes
>>>>>>>> not included) and keep Regular Expressions on.
>>>>>>>> But I do not know what is code for space
>>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> KG01 - Why is this so complicated. Such system language hides the
>>>>>> power of
>>>>>> the tool. The tool should understand natural language inputs.
>>>>>>
>>>>>
>>>>> I already thought the same. Regular expressions are mighty, but only
>>>>> (guessed) 5% of the users understand it (as with many mighty things).
>>>>> My
>>>>> first idea was to add buttons which add the 'coded' entries tothe
>>>>> expression, e.g.: Button 'Space' adds '\n' when pressed to the text
>>>>> field.
>>>>> Same for 'Start of Line' adding '^'. Much more to be defined, may
>>>>> someone
>>>>> knowing regular expressions well list more of them.
>>>>> Another way would be to allow tokens like <Space> which get translated
>>>>> to
>>>>> '\n' internally before using the expression, but then the user would
>>>>> again
>>>>> have to remember multiple tokens and how they are spelled (need to be
>>>>> valid, possible errors which need to be handled).
>>>>> Maybe a mix of both, press button 'Space' adds the (human readable)
>>>>> token
>>>>> <Space> which itself is not editable (represents a single character).
>>>>> Hmmm...
>>>>>
>>>>>
>>>> Have you seen what the SlickEdit coding editor has? Here is their
>>>> search dialog:
>>>>
>>>> http://people.apache.org/~**robweir/slickedit-re-dialog.**png<http://people.apache.org/%7Erobweir/slickedit-re-dialog.png>
>>>>
>>>> So you can click a button to pop out a list of common RE patterns.
>>>>
>>>
KG02 - This is great. Natural language for no techies. Readable tolkens is
what I was proposing, just didn't know what to call them ;)
KG02 - A further enhancement to this approach might be to allow the user to
construct a multi-dimensional query using the user friendly, readable
tolkens. For example, user could select <SPACE>, then <beginning of line>.
>>> Interesting. What is inserted into the text field, then? Some
>>> human-readable tokens, or the RE ones?
>>>
>>> But this is more of an aid to someone who already understands RE's.
>>>> I'm not sure we can do much to make this conceptually much easier for
>>>> end users, since regular expressions have a certain amount of
>>>> essential complexity. Or would it make sense to support more than one
>>>> RE variation, maybe full RE, but also DOS-style with only * and ?
>>>> qualifiers?
>>>>
>>>
>>> That is what MSDEV (Developer studio) does. It allows to choose between
>>> 'Wildcarts' and 'Regular expression', where the first one accepts simple
>>> '*' placeholders. An alternative for users, but limited. Maybe a good
>>> compromize...
>>>
>>> -Rob
>>>>
>>>>
>>>> Perhaps we could explore ways to provide such system-oriented syntax
>>>>>> to the
>>>>>> user in the context of the task. In other words, update the UI
>>>>>> design to
>>>>>> include a way to evoke a cheat sheet, or even better, implement a way
>>>>>> for
>>>>>> the user to insert syntax using natural language, with the system
>>>>>> interpreting behind the scenes.
>>>>>>
>>>>>> I suppose this is a broader usability theme that appears throughout
>>>>>> the
>>>>>> toolset. We should explore ways reduce the complexity of
>>>>>> system-oriented
>>>>>> command inputs and make advanced capabilities more consumable to less
>>>>>> technical users.
>>>>>>
>>>>>> After all, this is a tool to help people capture their thoughts and
>>>>>> share
>>>>>> ideas - not a development environment.
>>>>>>
>>>>>> Thoughts?
>>>>>>
>>>>>> Can any one let me know?
>>>>>>>
>>>>>>>> seena
>>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> If you are using a carriage return (shift+<Enter>) or <Enter>,
>>>>>>> you can
>>>>>>> use this: "^ " (^ followed by a space). Regular Expressions must
>>>>>>> be on.
>>>>>>> The replace box should be empty.
>>>>>>> Search and replace as you did using "\n" above.
>>>>>>>
>>>>>>> --Dan
>>>>>>>
>>>>>>> ------------------------------****----------------------------**
>>>>>>> --**---------
>>>>>>> To unsubscribe, e-mail: ooo-users-unsubscribe@**incubator.apache.org<oo...@incubator.apache.org>
>>>>>>> For additional commands, e-mail: ooo-users-help@incubator.**
>>>>>>> apache.org <oo...@incubator.apache.org>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>
>>>>> --
>>>>> ALG
>>>>>
>>>>>
>>>>> ------------------------------**------------------------------**
>>>>> ---------
>>>>> To unsubscribe, e-mail: ooo-users-unsubscribe@**incubator.apache.org<oo...@incubator.apache.org>
>>>>> For additional commands, e-mail: ooo-users-help@incubator.**apache.org<oo...@incubator.apache.org>
>>>>>
>>>>>
>>>
>>> --
>>> ALG
>>>
>>>
>>> ------------------------------**------------------------------**
>>> ---------
>>> To unsubscribe, e-mail: ooo-users-unsubscribe@**incubator.apache.org<oo...@incubator.apache.org>
>>> For additional commands, e-mail: ooo-users-help@incubator.**apache.org<oo...@incubator.apache.org>
>>>
>>>
>>>
>> Perhaps a valid solution might be a rewrite of Find and Replace,
>> simplifying it and allowing it to use various tokens so that Regular
>> Expression usage was completely concealed or even disabled.
>>
>> Then add (if permitted by the author) AltSearch,
>> http://extensions.services.**openoffice.org/en/search/node/**altsearch<http://extensions.services.openoffice.org/en/search/node/altsearch>
>> or advise its download as an extension; this is a much more powerful
>> mechanism and which could be available but out of the way of the
>> inexperienced User.
>>
>>
>
>
> ------------------------------**------------------------------**---------
> To unsubscribe, e-mail: ooo-users-unsubscribe@**incubator.apache.org<oo...@incubator.apache.org>
> For additional commands, e-mail: ooo-users-help@incubator.**apache.org<oo...@incubator.apache.org>
>
>
Re: Space before every line
Posted by Guenter Marxen <gu...@googlemail.com>.
Hello,
if I recall correctly, there is only spoken of space before (or perhaps
after) a "text line" in Writer.
There are paragraph attributes in (german) "Einzüge und Abstände"
(perhaps in English 'Indents and Distances") "Abstand Über" or "Unter
Absatz" (Engl. perhaps Distence above / under) and "Zeilenabstand"
(perhaps "line distance").
Perhaps you control the parapraph attributes?
MfG
G. Marxen
Am 28.06.2012 18:55, schrieb Rory O'Farrell:
> On Thu, 28 Jun 2012 16:45:54 +0000 (UTC)
> Armin Le Grand <Ar...@me.com> wrote:
>
>> Rob Weir <ro...@apache.org> wrote:
>>> On Thu, Jun 28, 2012 at 6:57 AM, Armin Le Grand <Ar...@me.com> wrote:
>>>> Hi Kevin,
>>>>
>>>> Kevin Grignon <ke...@gmail.com> wrote:
>>>>> KG01-see comments inline.
>>>>>
>>>>> On Thursday, June 28, 2012, Dan wrote:
>>>>>
>>>>>> Srinivasulu Bhattaram wrote:
>>>>>>
>>>>>>> I have a text file, which has one space before every line
>>>>>>> How to remove this using search and replace option
>>>>>>> For carriage return or <Enter>, I learnt that we hould use "\n" (quotes
>>>>>>> not included) and keep Regular Expressions on.
>>>>>>> But I do not know what is code for space
>>>>>>
>>>>>>
>>>>> KG01 - Why is this so complicated. Such system language hides the power of
>>>>> the tool. The tool should understand natural language inputs.
>>>>
>>>> I already thought the same. Regular expressions are mighty, but only
>>>> (guessed) 5% of the users understand it (as with many mighty things). My
>>>> first idea was to add buttons which add the 'coded' entries tothe
>>>> expression, e.g.: Button 'Space' adds '\n' when pressed to the text field.
>>>> Same for 'Start of Line' adding '^'. Much more to be defined, may someone
>>>> knowing regular expressions well list more of them.
>>>> Another way would be to allow tokens like <Space> which get translated to
>>>> '\n' internally before using the expression, but then the user would again
>>>> have to remember multiple tokens and how they are spelled (need to be
>>>> valid, possible errors which need to be handled).
>>>> Maybe a mix of both, press button 'Space' adds the (human readable) token
>>>> <Space> which itself is not editable (represents a single character).
>>>> Hmmm...
>>>>
>>>
>>> Have you seen what the SlickEdit coding editor has? Here is their
>>> search dialog:
>>>
>>> http://people.apache.org/~robweir/slickedit-re-dialog.png
>>>
>>> So you can click a button to pop out a list of common RE patterns.
>>
>> Interesting. What is inserted into the text field, then? Some
>> human-readable tokens, or the RE ones?
>>
>>> But this is more of an aid to someone who already understands RE's.
>>> I'm not sure we can do much to make this conceptually much easier for
>>> end users, since regular expressions have a certain amount of
>>> essential complexity. Or would it make sense to support more than one
>>> RE variation, maybe full RE, but also DOS-style with only * and ?
>>> qualifiers?
>>
>> That is what MSDEV (Developer studio) does. It allows to choose between
>> 'Wildcarts' and 'Regular expression', where the first one accepts simple
>> '*' placeholders. An alternative for users, but limited. Maybe a good
>> compromize...
>>
>>> -Rob
>>>
>>>
>>>>> Perhaps we could explore ways to provide such system-oriented syntax to the
>>>>> user in the context of the task. In other words, update the UI design to
>>>>> include a way to evoke a cheat sheet, or even better, implement a way for
>>>>> the user to insert syntax using natural language, with the system
>>>>> interpreting behind the scenes.
>>>>>
>>>>> I suppose this is a broader usability theme that appears throughout the
>>>>> toolset. We should explore ways reduce the complexity of system-oriented
>>>>> command inputs and make advanced capabilities more consumable to less
>>>>> technical users.
>>>>>
>>>>> After all, this is a tool to help people capture their thoughts and share
>>>>> ideas - not a development environment.
>>>>>
>>>>> Thoughts?
>>>>>
>>>>>> Can any one let me know?
>>>>>>> seena
>>>>>>
>>>>>>
>>>>>> If you are using a carriage return (shift+<Enter>) or <Enter>, you can
>>>>>> use this: "^ " (^ followed by a space). Regular Expressions must be on.
>>>>>> The replace box should be empty.
>>>>>> Search and replace as you did using "\n" above.
>>>>>>
>>>>>> --Dan
>>>>>>
>>>>>> ------------------------------**------------------------------**---------
>>>>>> To unsubscribe, e-mail: ooo-users-unsubscribe@incubator.apache.org
>>>>>> For additional commands, e-mail: ooo-users-help@incubator.apache.org
>>>>>>
>>>>>>
>>>>
>>>>
>>>> --
>>>> ALG
>>>>
>>>>
>>>> ---------------------------------------------------------------------
>>>> To unsubscribe, e-mail: ooo-users-unsubscribe@incubator.apache.org
>>>> For additional commands, e-mail: ooo-users-help@incubator.apache.org
>>>>
>>
>>
>> --
>> ALG
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: ooo-users-unsubscribe@incubator.apache.org
>> For additional commands, e-mail: ooo-users-help@incubator.apache.org
>>
>>
>
> Perhaps a valid solution might be a rewrite of Find and Replace, simplifying it and allowing it to use various tokens so that Regular Expression usage was completely concealed or even disabled.
>
> Then add (if permitted by the author) AltSearch,
> http://extensions.services.openoffice.org/en/search/node/altsearch
> or advise its download as an extension; this is a much more powerful mechanism and which could be available but out of the way of the inexperienced User.
>
---------------------------------------------------------------------
To unsubscribe, e-mail: ooo-users-unsubscribe@incubator.apache.org
For additional commands, e-mail: ooo-users-help@incubator.apache.org
Re: Space before every line
Posted by Rory O'Farrell <of...@iol.ie>.
On Thu, 28 Jun 2012 16:45:54 +0000 (UTC)
Armin Le Grand <Ar...@me.com> wrote:
> Rob Weir <ro...@apache.org> wrote:
> > On Thu, Jun 28, 2012 at 6:57 AM, Armin Le Grand <Ar...@me.com> wrote:
> >> Hi Kevin,
> >>
> >> Kevin Grignon <ke...@gmail.com> wrote:
> >>> KG01-see comments inline.
> >>>
> >>> On Thursday, June 28, 2012, Dan wrote:
> >>>
> >>>> Srinivasulu Bhattaram wrote:
> >>>>
> >>>>> I have a text file, which has one space before every line
> >>>>> How to remove this using search and replace option
> >>>>> For carriage return or <Enter>, I learnt that we hould use "\n" (quotes
> >>>>> not included) and keep Regular Expressions on.
> >>>>> But I do not know what is code for space
> >>>>
> >>>>
> >>> KG01 - Why is this so complicated. Such system language hides the power of
> >>> the tool. The tool should understand natural language inputs.
> >>
> >> I already thought the same. Regular expressions are mighty, but only
> >> (guessed) 5% of the users understand it (as with many mighty things). My
> >> first idea was to add buttons which add the 'coded' entries tothe
> >> expression, e.g.: Button 'Space' adds '\n' when pressed to the text field.
> >> Same for 'Start of Line' adding '^'. Much more to be defined, may someone
> >> knowing regular expressions well list more of them.
> >> Another way would be to allow tokens like <Space> which get translated to
> >> '\n' internally before using the expression, but then the user would again
> >> have to remember multiple tokens and how they are spelled (need to be
> >> valid, possible errors which need to be handled).
> >> Maybe a mix of both, press button 'Space' adds the (human readable) token
> >> <Space> which itself is not editable (represents a single character).
> >> Hmmm...
> >>
> >
> > Have you seen what the SlickEdit coding editor has? Here is their
> > search dialog:
> >
> > http://people.apache.org/~robweir/slickedit-re-dialog.png
> >
> > So you can click a button to pop out a list of common RE patterns.
>
> Interesting. What is inserted into the text field, then? Some
> human-readable tokens, or the RE ones?
>
> > But this is more of an aid to someone who already understands RE's.
> > I'm not sure we can do much to make this conceptually much easier for
> > end users, since regular expressions have a certain amount of
> > essential complexity. Or would it make sense to support more than one
> > RE variation, maybe full RE, but also DOS-style with only * and ?
> > qualifiers?
>
> That is what MSDEV (Developer studio) does. It allows to choose between
> 'Wildcarts' and 'Regular expression', where the first one accepts simple
> '*' placeholders. An alternative for users, but limited. Maybe a good
> compromize...
>
> > -Rob
> >
> >
> >>> Perhaps we could explore ways to provide such system-oriented syntax to the
> >>> user in the context of the task. In other words, update the UI design to
> >>> include a way to evoke a cheat sheet, or even better, implement a way for
> >>> the user to insert syntax using natural language, with the system
> >>> interpreting behind the scenes.
> >>>
> >>> I suppose this is a broader usability theme that appears throughout the
> >>> toolset. We should explore ways reduce the complexity of system-oriented
> >>> command inputs and make advanced capabilities more consumable to less
> >>> technical users.
> >>>
> >>> After all, this is a tool to help people capture their thoughts and share
> >>> ideas - not a development environment.
> >>>
> >>> Thoughts?
> >>>
> >>>> Can any one let me know?
> >>>>> seena
> >>>>
> >>>>
> >>>> If you are using a carriage return (shift+<Enter>) or <Enter>, you can
> >>>> use this: "^ " (^ followed by a space). Regular Expressions must be on.
> >>>> The replace box should be empty.
> >>>> Search and replace as you did using "\n" above.
> >>>>
> >>>> --Dan
> >>>>
> >>>> ------------------------------**------------------------------**---------
> >>>> To unsubscribe, e-mail: ooo-users-unsubscribe@incubator.apache.org
> >>>> For additional commands, e-mail: ooo-users-help@incubator.apache.org
> >>>>
> >>>>
> >>
> >>
> >> --
> >> ALG
> >>
> >>
> >> ---------------------------------------------------------------------
> >> To unsubscribe, e-mail: ooo-users-unsubscribe@incubator.apache.org
> >> For additional commands, e-mail: ooo-users-help@incubator.apache.org
> >>
>
>
> --
> ALG
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: ooo-users-unsubscribe@incubator.apache.org
> For additional commands, e-mail: ooo-users-help@incubator.apache.org
>
>
Perhaps a valid solution might be a rewrite of Find and Replace, simplifying it and allowing it to use various tokens so that Regular Expression usage was completely concealed or even disabled.
Then add (if permitted by the author) AltSearch,
http://extensions.services.openoffice.org/en/search/node/altsearch
or advise its download as an extension; this is a much more powerful mechanism and which could be available but out of the way of the inexperienced User.
--
Rory O'Farrell <of...@iol.ie>
---------------------------------------------------------------------
To unsubscribe, e-mail: ooo-users-unsubscribe@incubator.apache.org
For additional commands, e-mail: ooo-users-help@incubator.apache.org
Re: Space before every line
Posted by Armin Le Grand <Ar...@me.com>.
Rob Weir <ro...@apache.org> wrote:
> On Thu, Jun 28, 2012 at 6:57 AM, Armin Le Grand <Ar...@me.com> wrote:
>> Hi Kevin,
>>
>> Kevin Grignon <ke...@gmail.com> wrote:
>>> KG01-see comments inline.
>>>
>>> On Thursday, June 28, 2012, Dan wrote:
>>>
>>>> Srinivasulu Bhattaram wrote:
>>>>
>>>>> I have a text file, which has one space before every line
>>>>> How to remove this using search and replace option
>>>>> For carriage return or <Enter>, I learnt that we hould use "\n" (quotes
>>>>> not included) and keep Regular Expressions on.
>>>>> But I do not know what is code for space
>>>>
>>>>
>>> KG01 - Why is this so complicated. Such system language hides the power of
>>> the tool. The tool should understand natural language inputs.
>>
>> I already thought the same. Regular expressions are mighty, but only
>> (guessed) 5% of the users understand it (as with many mighty things). My
>> first idea was to add buttons which add the 'coded' entries tothe
>> expression, e.g.: Button 'Space' adds '\n' when pressed to the text field.
>> Same for 'Start of Line' adding '^'. Much more to be defined, may someone
>> knowing regular expressions well list more of them.
>> Another way would be to allow tokens like <Space> which get translated to
>> '\n' internally before using the expression, but then the user would again
>> have to remember multiple tokens and how they are spelled (need to be
>> valid, possible errors which need to be handled).
>> Maybe a mix of both, press button 'Space' adds the (human readable) token
>> <Space> which itself is not editable (represents a single character).
>> Hmmm...
>>
>
> Have you seen what the SlickEdit coding editor has? Here is their
> search dialog:
>
> http://people.apache.org/~robweir/slickedit-re-dialog.png
>
> So you can click a button to pop out a list of common RE patterns.
Interesting. What is inserted into the text field, then? Some
human-readable tokens, or the RE ones?
> But this is more of an aid to someone who already understands RE's.
> I'm not sure we can do much to make this conceptually much easier for
> end users, since regular expressions have a certain amount of
> essential complexity. Or would it make sense to support more than one
> RE variation, maybe full RE, but also DOS-style with only * and ?
> qualifiers?
That is what MSDEV (Developer studio) does. It allows to choose between
'Wildcarts' and 'Regular expression', where the first one accepts simple
'*' placeholders. An alternative for users, but limited. Maybe a good
compromize...
> -Rob
>
>
>>> Perhaps we could explore ways to provide such system-oriented syntax to the
>>> user in the context of the task. In other words, update the UI design to
>>> include a way to evoke a cheat sheet, or even better, implement a way for
>>> the user to insert syntax using natural language, with the system
>>> interpreting behind the scenes.
>>>
>>> I suppose this is a broader usability theme that appears throughout the
>>> toolset. We should explore ways reduce the complexity of system-oriented
>>> command inputs and make advanced capabilities more consumable to less
>>> technical users.
>>>
>>> After all, this is a tool to help people capture their thoughts and share
>>> ideas - not a development environment.
>>>
>>> Thoughts?
>>>
>>>> Can any one let me know?
>>>>> seena
>>>>
>>>>
>>>> If you are using a carriage return (shift+<Enter>) or <Enter>, you can
>>>> use this: "^ " (^ followed by a space). Regular Expressions must be on.
>>>> The replace box should be empty.
>>>> Search and replace as you did using "\n" above.
>>>>
>>>> --Dan
>>>>
>>>> ------------------------------**------------------------------**---------
>>>> To unsubscribe, e-mail: ooo-users-unsubscribe@incubator.apache.org
>>>> For additional commands, e-mail: ooo-users-help@incubator.apache.org
>>>>
>>>>
>>
>>
>> --
>> ALG
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: ooo-users-unsubscribe@incubator.apache.org
>> For additional commands, e-mail: ooo-users-help@incubator.apache.org
>>
--
ALG
---------------------------------------------------------------------
To unsubscribe, e-mail: ooo-users-unsubscribe@incubator.apache.org
For additional commands, e-mail: ooo-users-help@incubator.apache.org
Re: Space before every line
Posted by Niall Martin <ni...@rndmartin.cix.co.uk>.
This user would very much like to have something like that. Something similar was a
feature of Lotus WordPro which was easy to use if you wanted to take out spaces and
carriage returns and the like and I miss it in OO.o
On 28 Jun 2012 at 18:48, Johnny Rosenberg wrote:
Send reply to: ooo-users@incubator.apache.org
Date sent: Thu, 28 Jun 2012 18:48:19 +0200
Subject: Re: Space before every line
From: Johnny Rosenberg <gu...@gmail.com>
To: ooo-users@incubator.apache.org
> I would guess that a non-regular-expression search and replace
> dialogue that supports things like \n, \t and maybe those joker
> characters would be enough for most users. Maybe with the addition of
> characters for page break and other types of breaks. Those could be
> available in a listbox or something.
>
> Maybe \n would not be an obvious syntax for non programmers, so
> another approach would probably be something like [newline],
> selectable in a list box.
>
> For example, the user want to find a space after a new line:
> 1. Select New line in the list box, click Add (or whatever a
> proper name for the button would be) or just double click New line
> in the list box. 2. The entry field now looks like: [newline] (or
> maybe <newline> or whatever is decided to be a good syntax). 3. The
> user press the space key or select Space from the list box.
>
> When something is selected from the list box, the focus should remain
> in the input field, so the user can enter more stuff there without
> moving focus.
Niall Martin
Phone 0131 4678468
Please reply to: niall<at>rndmartin.cix.co.uk
---------------------------------------------------------------------
To unsubscribe, e-mail: ooo-users-unsubscribe@incubator.apache.org
For additional commands, e-mail: ooo-users-help@incubator.apache.org
Re: Space before every line
Posted by Klaus Muth <mu...@hagos.de>.
Am 28.06.2012 17:36, schrieb Rob Weir:
> On Thu, Jun 28, 2012 at 6:57 AM, Armin Le Grand <Ar...@me.com> wrote:
>> Hi Kevin,
>>
>> Kevin Grignon <ke...@gmail.com> wrote:
>>> KG01-see comments inline.
>>>
>>> On Thursday, June 28, 2012, Dan wrote:
>>>
>>>> Srinivasulu Bhattaram wrote:
>>>>
>>>>> I have a text file, which has one space before every line
>>>>> How to remove this using search and replace option
>>>>> For carriage return or <Enter>, I learnt that we hould use "\n" (quotes
>>>>> not included) and keep Regular Expressions on.
>>>>> But I do not know what is code for space
>>>>
>>>>
>>> KG01 - Why is this so complicated. Such system language hides the power of
>>> the tool. The tool should understand natural language inputs.
>>
>> I already thought the same. Regular expressions are mighty, but only
>> (guessed) 5% of the users understand it (as with many mighty things). My
>> first idea was to add buttons which add the 'coded' entries tothe
>> expression, e.g.: Button 'Space' adds '\n' when pressed to the text field.
>> Same for 'Start of Line' adding '^'. Much more to be defined, may someone
>> knowing regular expressions well list more of them.
>> Another way would be to allow tokens like <Space> which get translated to
>> '\n' internally before using the expression, but then the user would again
>> have to remember multiple tokens and how they are spelled (need to be
>> valid, possible errors which need to be handled).
>> Maybe a mix of both, press button 'Space' adds the (human readable) token
>> <Space> which itself is not editable (represents a single character).
>> Hmmm...
>>
>
> Have you seen what the SlickEdit coding editor has? Here is their
> search dialog:
What about this one: http://www.blackie.dk/KDE/KRegExpEditor/ ?
Freundliche Grüße
--
Klaus Muth
HAGOS eG EDV Tel: (+49) 711/78805-7085
Zentrale Stuttgart Industriestr. 62 Fax: (+49) 711/78805-7035
http://www.hagos.de 70565 Stuttgart muth@hagos.de
HAGOS Verbund deutscher Kachelofen- und Luftheizungsbauerbetriebe eG
Sitz: Stuttgart
Rechtsform: Genossenschaft
Registergericht: Stuttgart GnR 77
Vorstände: Guido Eichel, Ralf Tigges
Aufsichtsratsvorsitzender: Thomas Müller
USt.-ID-Nr.: DE 147799748
---------------------------------------------------------------------
To unsubscribe, e-mail: ooo-users-unsubscribe@incubator.apache.org
For additional commands, e-mail: ooo-users-help@incubator.apache.org
Re: Space before every line
Posted by Johnny Rosenberg <gu...@gmail.com>.
2012/6/28 Rob Weir <ro...@apache.org>:
> On Thu, Jun 28, 2012 at 6:57 AM, Armin Le Grand <Ar...@me.com> wrote:
>> Hi Kevin,
>>
>> Kevin Grignon <ke...@gmail.com> wrote:
>>> KG01-see comments inline.
>>>
>>> On Thursday, June 28, 2012, Dan wrote:
>>>
>>>> Srinivasulu Bhattaram wrote:
>>>>
>>>>> I have a text file, which has one space before every line
>>>>> How to remove this using search and replace option
>>>>> For carriage return or <Enter>, I learnt that we hould use "\n" (quotes
>>>>> not included) and keep Regular Expressions on.
>>>>> But I do not know what is code for space
>>>>
>>>>
>>> KG01 - Why is this so complicated. Such system language hides the power of
>>> the tool. The tool should understand natural language inputs.
>>
>> I already thought the same. Regular expressions are mighty, but only
>> (guessed) 5% of the users understand it (as with many mighty things). My
>> first idea was to add buttons which add the 'coded' entries tothe
>> expression, e.g.: Button 'Space' adds '\n' when pressed to the text field.
>> Same for 'Start of Line' adding '^'. Much more to be defined, may someone
>> knowing regular expressions well list more of them.
>> Another way would be to allow tokens like <Space> which get translated to
>> '\n' internally before using the expression, but then the user would again
>> have to remember multiple tokens and how they are spelled (need to be
>> valid, possible errors which need to be handled).
>> Maybe a mix of both, press button 'Space' adds the (human readable) token
>> <Space> which itself is not editable (represents a single character).
>> Hmmm...
>>
>
> Have you seen what the SlickEdit coding editor has? Here is their
> search dialog:
>
> http://people.apache.org/~robweir/slickedit-re-dialog.png
>
> So you can click a button to pop out a list of common RE patterns.
>
> But this is more of an aid to someone who already understands RE's.
> I'm not sure we can do much to make this conceptually much easier for
> end users, since regular expressions have a certain amount of
> essential complexity. Or would it make sense to support more than one
> RE variation, maybe full RE, but also DOS-style with only * and ?
> qualifiers?
>
> -Rob
I would guess that a non-regular-expression search and replace
dialogue that supports things like \n, \t and maybe those joker
characters would be enough for most users. Maybe with the addition of
characters for page break and other types of breaks. Those could be
available in a listbox or something.
Maybe ”\n” would not be an obvious syntax for non programmers, so
another approach would probably be something like [newline],
selectable in a list box.
For example, the user want to find a space after a new line:
1. Select ”New line” in the list box, click ”Add” (or whatever a
proper name for the button would be) or just double click ”New line”
in the list box.
2. The entry field now looks like: [newline] (or maybe <newline> or
whatever is decided to be a good syntax).
3. The user press the space key or select ”Space” from the list box.
When something is selected from the list box, the focus should remain
in the input field, so the user can enter more stuff there without
moving focus.
Of course regular expressions doesn't have to be removed. Adding a
feature doesn't necessarily mean removing another feature.
Kind regards
Johnny Rosenberg
ジョニー・ローゼンバーグ
>
>
>>> Perhaps we could explore ways to provide such system-oriented syntax to the
>>> user in the context of the task. In other words, update the UI design to
>>> include a way to evoke a cheat sheet, or even better, implement a way for
>>> the user to insert syntax using natural language, with the system
>>> interpreting behind the scenes.
>>>
>>> I suppose this is a broader usability theme that appears throughout the
>>> toolset. We should explore ways reduce the complexity of system-oriented
>>> command inputs and make advanced capabilities more consumable to less
>>> technical users.
>>>
>>> After all, this is a tool to help people capture their thoughts and share
>>> ideas - not a development environment.
>>>
>>> Thoughts?
>>>
>>>> Can any one let me know?
>>>>> seena
>>>>
>>>>
>>>> If you are using a carriage return (shift+<Enter>) or <Enter>, you can
>>>> use this: "^ " (^ followed by a space). Regular Expressions must be on.
>>>> The replace box should be empty.
>>>> Search and replace as you did using "\n" above.
>>>>
>>>> --Dan
>>>>
>>>> ------------------------------**------------------------------**---------
>>>> To unsubscribe, e-mail: ooo-users-unsubscribe@incubator.apache.org
>>>> For additional commands, e-mail: ooo-users-help@incubator.apache.org
>>>>
>>>>
>>
>>
>> --
>> ALG
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: ooo-users-unsubscribe@incubator.apache.org
>> For additional commands, e-mail: ooo-users-help@incubator.apache.org
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: ooo-users-unsubscribe@incubator.apache.org
> For additional commands, e-mail: ooo-users-help@incubator.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: ooo-users-unsubscribe@incubator.apache.org
For additional commands, e-mail: ooo-users-help@incubator.apache.org
Re: Space before every line
Posted by Rob Weir <ro...@apache.org>.
On Thu, Jun 28, 2012 at 6:57 AM, Armin Le Grand <Ar...@me.com> wrote:
> Hi Kevin,
>
> Kevin Grignon <ke...@gmail.com> wrote:
>> KG01-see comments inline.
>>
>> On Thursday, June 28, 2012, Dan wrote:
>>
>>> Srinivasulu Bhattaram wrote:
>>>
>>>> I have a text file, which has one space before every line
>>>> How to remove this using search and replace option
>>>> For carriage return or <Enter>, I learnt that we hould use "\n" (quotes
>>>> not included) and keep Regular Expressions on.
>>>> But I do not know what is code for space
>>>
>>>
>> KG01 - Why is this so complicated. Such system language hides the power of
>> the tool. The tool should understand natural language inputs.
>
> I already thought the same. Regular expressions are mighty, but only
> (guessed) 5% of the users understand it (as with many mighty things). My
> first idea was to add buttons which add the 'coded' entries tothe
> expression, e.g.: Button 'Space' adds '\n' when pressed to the text field.
> Same for 'Start of Line' adding '^'. Much more to be defined, may someone
> knowing regular expressions well list more of them.
> Another way would be to allow tokens like <Space> which get translated to
> '\n' internally before using the expression, but then the user would again
> have to remember multiple tokens and how they are spelled (need to be
> valid, possible errors which need to be handled).
> Maybe a mix of both, press button 'Space' adds the (human readable) token
> <Space> which itself is not editable (represents a single character).
> Hmmm...
>
Have you seen what the SlickEdit coding editor has? Here is their
search dialog:
http://people.apache.org/~robweir/slickedit-re-dialog.png
So you can click a button to pop out a list of common RE patterns.
But this is more of an aid to someone who already understands RE's.
I'm not sure we can do much to make this conceptually much easier for
end users, since regular expressions have a certain amount of
essential complexity. Or would it make sense to support more than one
RE variation, maybe full RE, but also DOS-style with only * and ?
qualifiers?
-Rob
>> Perhaps we could explore ways to provide such system-oriented syntax to the
>> user in the context of the task. In other words, update the UI design to
>> include a way to evoke a cheat sheet, or even better, implement a way for
>> the user to insert syntax using natural language, with the system
>> interpreting behind the scenes.
>>
>> I suppose this is a broader usability theme that appears throughout the
>> toolset. We should explore ways reduce the complexity of system-oriented
>> command inputs and make advanced capabilities more consumable to less
>> technical users.
>>
>> After all, this is a tool to help people capture their thoughts and share
>> ideas - not a development environment.
>>
>> Thoughts?
>>
>>> Can any one let me know?
>>>> seena
>>>
>>>
>>> If you are using a carriage return (shift+<Enter>) or <Enter>, you can
>>> use this: "^ " (^ followed by a space). Regular Expressions must be on.
>>> The replace box should be empty.
>>> Search and replace as you did using "\n" above.
>>>
>>> --Dan
>>>
>>> ------------------------------**------------------------------**---------
>>> To unsubscribe, e-mail: ooo-users-unsubscribe@incubator.apache.org
>>> For additional commands, e-mail: ooo-users-help@incubator.apache.org
>>>
>>>
>
>
> --
> ALG
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: ooo-users-unsubscribe@incubator.apache.org
> For additional commands, e-mail: ooo-users-help@incubator.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: ooo-users-unsubscribe@incubator.apache.org
For additional commands, e-mail: ooo-users-help@incubator.apache.org
Re: Space before every line
Posted by Armin Le Grand <Ar...@me.com>.
Hi Kevin,
Kevin Grignon <ke...@gmail.com> wrote:
> KG01-see comments inline.
>
> On Thursday, June 28, 2012, Dan wrote:
>
>> Srinivasulu Bhattaram wrote:
>>
>>> I have a text file, which has one space before every line
>>> How to remove this using search and replace option
>>> For carriage return or <Enter>, I learnt that we hould use "\n" (quotes
>>> not included) and keep Regular Expressions on.
>>> But I do not know what is code for space
>>
>>
> KG01 - Why is this so complicated. Such system language hides the power of
> the tool. The tool should understand natural language inputs.
I already thought the same. Regular expressions are mighty, but only
(guessed) 5% of the users understand it (as with many mighty things). My
first idea was to add buttons which add the 'coded' entries tothe
expression, e.g.: Button 'Space' adds '\n' when pressed to the text field.
Same for 'Start of Line' adding '^'. Much more to be defined, may someone
knowing regular expressions well list more of them.
Another way would be to allow tokens like <Space> which get translated to
'\n' internally before using the expression, but then the user would again
have to remember multiple tokens and how they are spelled (need to be
valid, possible errors which need to be handled).
Maybe a mix of both, press button 'Space' adds the (human readable) token
<Space> which itself is not editable (represents a single character).
Hmmm...
> Perhaps we could explore ways to provide such system-oriented syntax to the
> user in the context of the task. In other words, update the UI design to
> include a way to evoke a cheat sheet, or even better, implement a way for
> the user to insert syntax using natural language, with the system
> interpreting behind the scenes.
>
> I suppose this is a broader usability theme that appears throughout the
> toolset. We should explore ways reduce the complexity of system-oriented
> command inputs and make advanced capabilities more consumable to less
> technical users.
>
> After all, this is a tool to help people capture their thoughts and share
> ideas - not a development environment.
>
> Thoughts?
>
>> Can any one let me know?
>>> seena
>>
>>
>> If you are using a carriage return (shift+<Enter>) or <Enter>, you can
>> use this: "^ " (^ followed by a space). Regular Expressions must be on.
>> The replace box should be empty.
>> Search and replace as you did using "\n" above.
>>
>> --Dan
>>
>> ------------------------------**------------------------------**---------
>> To unsubscribe, e-mail: ooo-users-unsubscribe@incubator.apache.org
>> For additional commands, e-mail: ooo-users-help@incubator.apache.org
>>
>>
--
ALG
---------------------------------------------------------------------
To unsubscribe, e-mail: ooo-users-unsubscribe@incubator.apache.org
For additional commands, e-mail: ooo-users-help@incubator.apache.org
Re: Space before every line
Posted by Klaus Muth <mu...@hagos.de>.
Am 28.06.2012 04:46, schrieb Kevin Grignon:
> On Thursday, June 28, 2012, Dan wrote:
>> Srinivasulu Bhattaram wrote:
>>> I have a text file, which has one space before every line
>>> How to remove this using search and replace option
>>> For carriage return or <Enter>, I learnt that we hould use "\n" (quotes
>>> not included) and keep Regular Expressions on.
>>> But I do not know what is code for space
>>
> KG01 - Why is this so complicated. Such system language hides the power of
> the tool. The tool should understand natural language inputs.
This is complicated, because you use regular expressions. Regular expressions
are complicated. I'm very fond of them and I'm really glad there is an option
to use them.
Most users will be happy with simple matching.
Freundliche Grüße
--
Klaus Muth
HAGOS eG EDV Tel: (+49) 711/78805-7085
Zentrale Stuttgart Industriestr. 62 Fax: (+49) 711/78805-7035
http://www.hagos.de 70565 Stuttgart muth@hagos.de
HAGOS Verbund deutscher Kachelofen- und Luftheizungsbauerbetriebe eG
Sitz: Stuttgart
Rechtsform: Genossenschaft
Registergericht: Stuttgart GnR 77
Vorstände: Guido Eichel, Ralf Tigges
Aufsichtsratsvorsitzender: Thomas Müller
USt.-ID-Nr.: DE 147799748
---------------------------------------------------------------------
To unsubscribe, e-mail: ooo-users-unsubscribe@incubator.apache.org
For additional commands, e-mail: ooo-users-help@incubator.apache.org
Re: Space before every line
Posted by Kevin Grignon <ke...@gmail.com>.
KG01-see comments inline.
On Thursday, June 28, 2012, Dan wrote:
> Srinivasulu Bhattaram wrote:
>
>> I have a text file, which has one space before every line
>> How to remove this using search and replace option
>> For carriage return or <Enter>, I learnt that we hould use "\n" (quotes
>> not included) and keep Regular Expressions on.
>> But I do not know what is code for space
>
>
KG01 - Why is this so complicated. Such system language hides the power of
the tool. The tool should understand natural language inputs.
Perhaps we could explore ways to provide such system-oriented syntax to the
user in the context of the task. In other words, update the UI design to
include a way to evoke a cheat sheet, or even better, implement a way for
the user to insert syntax using natural language, with the system
interpreting behind the scenes.
I suppose this is a broader usability theme that appears throughout the
toolset. We should explore ways reduce the complexity of system-oriented
command inputs and make advanced capabilities more consumable to less
technical users.
After all, this is a tool to help people capture their thoughts and share
ideas - not a development environment.
Thoughts?
> Can any one let me know?
>> seena
>
>
> If you are using a carriage return (shift+<Enter>) or <Enter>, you can
> use this: "^ " (^ followed by a space). Regular Expressions must be on.
> The replace box should be empty.
> Search and replace as you did using "\n" above.
>
> --Dan
>
> ------------------------------**------------------------------**---------
> To unsubscribe, e-mail: ooo-users-unsubscribe@incubator.apache.org
> For additional commands, e-mail: ooo-users-help@incubator.apache.org
>
>
Re: Space before every line
Posted by Dan <el...@gmail.com>.
Srinivasulu Bhattaram wrote:
> I have a text file, which has one space before every line
> How to remove this using search and replace option
> For carriage return or <Enter>, I learnt that we hould use "\n"
> (quotes not included) and keep Regular Expressions on.
> But I do not know what is code for space
> Can any one let me know?
> seena
If you are using a carriage return (shift+<Enter>) or <Enter>, you
can use this: "^ " (^ followed by a space). Regular Expressions must
be on. The replace box should be empty.
Search and replace as you did using "\n" above.
--Dan
---------------------------------------------------------------------
To unsubscribe, e-mail: ooo-users-unsubscribe@incubator.apache.org
For additional commands, e-mail: ooo-users-help@incubator.apache.org