On 7/31/20 12:53 AM, Daniel wrote:
> On 2020-07-31 01:35, Andrew Parsloe wrote:
>> On 30/07/2020 11:29 pm, Daniel wrote:
>>> I find the Paste Recent context menu entry slightly distracting
>>> because it is pretty much at the top, so I always run with the mouse
&
On 2020-07-31 01:35, Andrew Parsloe wrote:
On 30/07/2020 11:29 pm, Daniel wrote:
I find the Paste Recent context menu entry slightly distracting
because it is pretty much at the top, so I always run with the mouse
over it, and it contains changing and possibly long text.
Maybe it would be
On 30/07/2020 11:29 pm, Daniel wrote:
I find the Paste Recent context menu entry slightly distracting
because it is pretty much at the top, so I always run with the mouse
over it, and it contains changing and possibly long text.
Maybe it would be enough to have this function in the Edit menu
I find the Paste Recent context menu entry slightly distracting because
it is pretty much at the top, so I always run with the mouse over it,
and it contains changing and possibly long text.
Maybe it would be enough to have this function in the Edit menu?
The Paste Recent is a very nice
Am Mittwoch, den 26.12.2018, 22:30 -0500 schrieb Scott Kostyshak:
> src/frontends/qt4/GuiToolbar.cpp: In member function ‘virtual void
> lyx::frontend::DynamicMenuButton::updateTriggered()’:
> src/frontends/qt4/GuiToolbar.cpp:398:12: error: variable
> ‘default_act’ set but not used [-Werror=unused-
On Wed, Dec 26, 2018 at 05:09:35PM +0100, Juergen Spitzmueller wrote:
> commit 9495ff665dff01a838304671232be40a3d5dca89
> Author: Juergen Spitzmueller
> Date: Wed Dec 26 17:11:24 2018 +0100
>
> Make "paste recent" accessible from toolbar
>
>
it menu generally operates on the current selection or
the implicit current selection identified by the blinking cursor.
So the user inside this menu will have the notion of "document
selection" in mind.
Paste extends along the time axis for selection by one step. Paste
Recent extends furt
John Levon <[EMAIL PROTECTED]> writes:
| "Open Recent" means "Open Recent [Document] blah.lyx". "Paste Recent"
| means "Paste Recent [selection that starts with] blah de blah..."
To me this seems almost seem like a ad-hoc explanation tuned to agre
John Levon <[EMAIL PROTECTED]> writes:
| On Sun, Jun 29, 2003 at 01:42:50PM +0200, Lars Gullik Bj?nnes wrote:
|
| > There is nothing in common between "Open Recent" and "Paste Recent",
| > OR has a list of recently opened documents. PR has a list of recently
| &g
On Sun, Jun 29, 2003 at 01:42:50PM +0200, Lars Gullik Bj?nnes wrote:
> There is nothing in common between "Open Recent" and "Paste Recent",
> OR has a list of recently opened documents. PR has a list of recently
> copied and cut selections, not a list of rec
On Mon, Jun 30, 2003 at 01:58:46PM +0200, Andre Poenitz wrote:
> > Lars> SO IMO "Paste Recent" is utterly misnamed. Unless I get strong
> > Lars> objections and well founded objections I am going to change this
> > Lars> to "Select and Paste".
I
Andre Poenitz wrote:
>
> Why not just let Lars commit what he wants and John change it later if he
> wants etc. There won't be consensus anyway.
And some more users on the devel front may comment, since it is then
more visible what this discussion is actually all about ;).
R.
On Mon, Jun 30, 2003 at 01:52:59PM +0200, Jean-Marc Lasgouttes wrote:
> >>>>> "Lars" == Lars Gullik Bjønnes <[EMAIL PROTECTED]> writes:
>
> Lars> SO IMO "Paste Recent" is utterly misnamed. Unless I get strong
> Lars> objections and w
>>>>> "Lars" == Lars Gullik Bjønnes <[EMAIL PROTECTED]> writes:
Lars> SO IMO "Paste Recent" is utterly misnamed. Unless I get strong
Lars> objections and well founded objections I am going to change this
Lars> to "Select and Paste".
Garst R. Reese wrote:
> What's wrong with:
> Paste C-v
> Paste... >
Tha answer I got to this: dithering. I didn't dare to ask more...
I would put "Pick & Paste", but partially because it sounds funny. ;^)
Regards, Alfredo
"Garst R. Reese" <[EMAIL PROTECTED]> writes:
| Lars Gullik Bjønnes wrote:
| >
| > "Garst R. Reese" <[EMAIL PROTECTED]> writes:
| > | What's wrong with:
| > | Paste C-v
| > | Paste... >
| > |
| > | ?
| >
| > IMHO too similar.
| >
| > but it is better than "Recent"
| >
| > --
| >
Lars Gullik Bjønnes wrote:
>
> "Garst R. Reese" <[EMAIL PROTECTED]> writes:
> | What's wrong with:
> | Paste C-v
> | Paste... >
> |
> | ?
>
> IMHO too similar.
>
> but it is better than "Recent"
>
> --
> Lgb
Well, I'm wondering why we have both. C-v could bring up the list if
"Garst R. Reese" <[EMAIL PROTECTED]> writes:
| Lars Gullik Bjønnes wrote:
| >
| > There is nothing in common between "Open Recent" and "Paste Recent",
| > OR has a list of recently opened documents. PR has a list of recently
| > copied and cut sele
Lars Gullik Bjønnes wrote:
>
> There is nothing in common between "Open Recent" and "Paste Recent",
> OR has a list of recently opened documents. PR has a list of recently
> copied and cut selections, not a list of recently pasted selections.
>
> SO IMO &quo
Alfredo Braunstein <[EMAIL PROTECTED]> writes:
| Lars Gullik Bjønnes wrote:
|
| > SO IMO "Paste Recent" is utterly misnamed. Unless I get strong
| > objections and well founded objections I am going to change this to
| > "Select and Paste".
|
| I find tha
Lars Gullik Bjønnes wrote:
> SO IMO "Paste Recent" is utterly misnamed. Unless I get strong
> objections and well founded objections I am going to change this to
> "Select and Paste".
I find that the "select" word is confusing in this context, because it se
There is nothing in common between "Open Recent" and "Paste Recent",
OR has a list of recently opened documents. PR has a list of recently
copied and cut selections, not a list of recently pasted selections.
SO IMO "Paste Recent" is utterly misnamed. Unless I
Lars Gullik Bjønnes wrote:
> The items are listed in reverse chronological order.
I do not write a log during work, and I will certainly use that great new
feature to insert a clipboard entry which I had pasted 1 hour ago. I know
that this is important for me (personally) because the ellipsis in
[EMAIL PROTECTED] (Juergen Spitzmueller) writes:
| Lars Gullik Bjønnes wrote:
| > Why is:
| >
| > "Once upon ... ever after"
| >
| > better than:
| >
| > "Once upon a time there..."
|
| Because I can copy two different (long) shapes of a phrase:
| a.) "Once upon a time there was a source maintain
Lars Gullik Bjønnes wrote:
> no you cannot...
> I do...
Ah yes sorry.
> I claim that this is of no importance.
Uffa. (childish italian interjection denoting contrariety)
> Why is:
>
> "Once upon ... ever after"
>
> better than:
>
> "Once upon a time there..."
>
> Remember that you yourse
Lars Gullik Bjønnes wrote:
> Why is:
>
> "Once upon ... ever after"
>
> better than:
>
> "Once upon a time there..."
Because I can copy two different (long) shapes of a phrase:
a.) "Once upon a time there was a source maintainer who instisted on the
theory that a string is string regardless of el
Alfredo Braunstein <[EMAIL PROTECTED]> writes:
| Lars Gullik Bjønnes wrote:
|
| > | Btw, I am a user, and I demand it! ;^)
| >
| > No :-) you are not a user.
|
| Oh I am... I use much more LyX from ~/doc than from ~/lyx-cvs/src! Selfish
| of me! ;^)
You are a user that disagrees with me so...
Alfredo Braunstein <[EMAIL PROTECTED]> writes:
| Lars Gullik Bjønnes wrote:
|
| > [EMAIL PROTECTED] (Lars Gullik Bjønnes) writes:
| >
| > | Alfredo Braunstein <[EMAIL PROTECTED]> writes:
| > |
| > | | Lars Gullik Bjønnes wrote:
| > | |
| > | | > This is more to my liking, but it is still
Lars Gullik Bjønnes wrote:
> | Btw, I am a user, and I demand it! ;^)
>
> No :-) you are not a user.
Oh I am... I use much more LyX from ~/doc than from ~/lyx-cvs/src! Selfish
of me! ;^)
Regards, Alfredo
Lars Gullik Bjønnes wrote:
> [EMAIL PROTECTED] (Lars Gullik Bjønnes) writes:
>
> | Alfredo Braunstein <[EMAIL PROTECTED]> writes:
> |
> | | Lars Gullik Bjønnes wrote:
> | |
> | | > This is more to my liking, but it is still a bit complex.
> | |
> | | Your patch seems nicer... (I don't like so
Alfredo Braunstein <[EMAIL PROTECTED]> writes:
| C'mon, shove in your patch. it's only 10 lines, and I find it's a cute &
| useful feature. And it's pretty damn isolated code... aren't you
| overreacting?
No... I do not think so...
| Btw, I am a user, and I demand it! ;^)
No :-) you are not a
[EMAIL PROTECTED] (Lars Gullik Bjønnes) writes:
| Alfredo Braunstein <[EMAIL PROTECTED]> writes:
|
| | Lars Gullik Bjønnes wrote:
| |
| | > This is more to my liking, but it is still a bit complex.
| |
| | Your patch seems nicer... (I don't like so much the fact that it has to
| | export all 1
Lars Gullik Bjønnes wrote:
> I am going to use a simpler solution, and only use what is in this
> patch if there is user demand.
C'mon, shove in your patch. it's only 10 lines, and I find it's a cute &
useful feature. And it's pretty damn isolated code... aren't you
overreacting?
Btw, I am a us
Alfredo Braunstein <[EMAIL PROTECTED]> writes:
| Lars Gullik Bjønnes wrote:
|
| > This is more to my liking, but it is still a bit complex.
|
| Your patch seems nicer... (I don't like so much the fact that it has to
| export all 10 full cut buffers to ascii to show the menu, but I suppose
| tha
Lars Gullik Bjønnes wrote:
> This is more to my liking, but it is still a bit complex.
Your patch seems nicer... (I don't like so much the fact that it has to
export all 10 full cut buffers to ascii to show the menu, but I suppose
that it's ok)
Regards, Alfredo
Lars Gullik Bjønnes wrote:
> and what you mean here is "frontpar.empty()"
Ok.
> And what if the second par also generates no output?
Can it? I though that no output was because of cutting the end of a par as
first thing (then only at the begin of the selection)
> Lets find a simpler solution
Lars Gullik Bjønnes wrote:
> I am not sure about the need.
It's cute!
> | b) the start and the end should be shown as they are better for
> |disambiguating a selection
>
> then you need to put the ellipsis at the middle of the selection not
> at the middle of the first 25 chars of the sel
Lars Gullik Bjønnes wrote:
> John Levon <[EMAIL PROTECTED]> writes:
>
> | On Tue, Jun 17, 2003 at 11:31:02PM +0200, Alfredo Braunstein wrote:
> |
> | > How about this one?
> |
> | Looks OK
> |
> | > + int size = pars.size();
> | > + if (frontpar.size() == 0) {
> | >
[EMAIL PROTECTED] (Lars Gullik Bjønnes) writes:
| Alfredo Braunstein <[EMAIL PROTECTED]> writes:
|
| | Alfredo Braunstein wrote:
| |
| | > John Levon wrote:
| | >
| | >> But the stuff you do with last par is better than what I did. We just
| | >> need to combine the two :)
| | >
| | > How abou
John Levon <[EMAIL PROTECTED]> writes:
| On Wed, Jun 18, 2003 at 12:53:02AM +0200, Lars Gullik Bj?nnes wrote:
|
| > is all of that really needed?
|
| Yes IMHO
|
| > | + shown = frontpar.substr(0, frontsize) + "..." +
| > | + backpar.substr(ba
On Wed, Jun 18, 2003 at 12:53:02AM +0200, Lars Gullik Bj?nnes wrote:
> is all of that really needed?
Yes IMHO
> | + shown = frontpar.substr(0, frontsize) + "..." +
> | + backpar.substr(backstart);
>
> And I am really not sure about that ellip
John Levon <[EMAIL PROTECTED]> writes:
| On Tue, Jun 17, 2003 at 11:31:02PM +0200, Alfredo Braunstein wrote:
|
| > How about this one?
|
| Looks OK
|
| > + int size = pars.size();
| > + if (frontpar.size() == 0) {
| > + frontpar = boost::next(pa
Alfredo Braunstein <[EMAIL PROTECTED]> writes:
| Alfredo Braunstein wrote:
|
| > John Levon wrote:
| >
| >> But the stuff you do with last par is better than what I did. We just
| >> need to combine the two :)
| >
| > How about this one?
|
| This one should actually work ;)
It looks way to co
On Tue, Jun 17, 2003 at 11:31:02PM +0200, Alfredo Braunstein wrote:
> How about this one?
Looks OK
> + int size = pars.size();
> + if (frontpar.size() == 0) {
> + frontpar = boost::next(pars.begin())->asString(&buffer,
> false);
> +
Alfredo Braunstein wrote:
> John Levon wrote:
>
>> But the stuff you do with last par is better than what I did. We just
>> need to combine the two :)
>
> How about this one?
This one should actually work ;)
Regards, Alfredo
Index: CutAndPaste.C
===
John Levon wrote:
> But the stuff you do with last par is better than what I did. We just
> need to combine the two :)
How about this one?
Index: CutAndPaste.C
===
RCS file: /usr/local/lyx/cvsroot/lyx-devel/src/CutAndPaste.C,v
retri
On Tue, Jun 17, 2003 at 10:26:48PM +0200, Alfredo Braunstein wrote:
> Sure, can you send yours (or tell me what to do to solve this. You look at
> the second par if the first is empty?) ?
I just appedn the second par if there is one.
But the stuff you do with last par is better than what I did.
On Tue, Jun 17, 2003 at 10:07:43PM +0200, Juergen Spitzmueller wrote:
> And you thought an empty patch fixes this. Fight fire with fire?
Three hundred sixty five degrees
Burning down the house !
/me goes to put on some Talking Heads :)
john
John Levon wrote:
> Darn, I've just done a patch too.
Oops sorry... I'm just too happy of having phone & adsl after more than 1
month (flat move umph...)
> I think we should combine both (yours can still show an empty entry if
> you select starting at the end of a line)
>
> Can you do this ?
John Levon wrote:
> I got empty entries because we only look at the first par.
And you thought an empty patch fixes this. Fight fire with fire?
Juergen.
On Tue, Jun 17, 2003 at 09:56:24PM +0200, Alfredo Braunstein wrote:
> What about this (ellipsis on the middle)?
Darn, I've just done a patch too.
I think we should combine both (yours can still show an empty entry if
you select starting at the end of a line)
Can you do this ?
regards
john
I got empty entries because we only look at the first par. This
adds a snoop into the second par. It also adds the ellipsis when needed.
OK ?
regards,
john
Lars Gullik Bjønnes wrote:
> John Levon <[EMAIL PROTECTED]> writes:
>
> | An ellipsis should be added to each entry that has been curtailed.
>
> I am not going to do that... I'll leave that for others.
What about this (ellipsis on the middle)?
Regards, Alfredo
Index: CutAndPaste.C
===
On Tue, Jun 17, 2003 at 07:08:25PM +0200, Lars Gullik Bj?nnes wrote:
> | I got some blank entries on my first test, but I don't know how
>
> paragraphs with only a inset that does not handle ascii.
Nope, I did it somehow with normal text and a list para
john
John Levon wrote:
> An ellipsis should be added to each entry that has been curtailed.
And the ellipsis should be in the middle of the string (like in klipper):
to be or...the question
> I got some blank entries on my first test, but I don't know how
I get blank entries with (some) insets (e.g.
An ellipsis should be added to each entry that has been curtailed.
I got some blank entries on my first test, but I don't know how
regards
john
56 matches
Mail list logo
