On 11/23/20 2:28 PM, Denis Shaposhnikov wrote:
On 23/11/2020 23:16, Samuel Sieb wrote:
Which is still the same answer I gave. Those are bash shortcuts which
are supposed to use ALT. I suspect that gnome-terminal was mapping Meta
OK, the question is how to change it and configure using of
On 23/11/2020 23:16, Samuel Sieb wrote:
Which is still the same answer I gave. Those are bash shortcuts which
are supposed to use ALT. I suspect that gnome-terminal was mapping Meta
OK, the question is how to change it and configure using of Win keys
instead of Alt keys? BTW, I don'
On 11/23/20 1:47 PM, Denis Shaposhnikov wrote:
On 23/11/2020 22:04, Samuel Sieb wrote:
From the gnome-terminal help, it says that alt-backspace is the
*bash* shortcut to delete the previous word. So the current behaviour is
Alt-backspace is just an example. Another example is navigation by
On 23/11/2020 22:04, Samuel Sieb wrote:
From the gnome-terminal help, it says that alt-backspace is the *bash*
shortcut to delete the previous word. So the current behaviour is
Alt-backspace is just an example. Another example is navigation by
words. In F32 it was Win+F/Win-B for forward
On 11/23/20 8:07 AM, Denis Shaposhnikov wrote:
After upgrade my Fedora from 32 to 33 I found Meta key in the
gnome-terminal works strange. Looks like now the gnome-terminal
recognizes Alt key as Meta key. Everywhere in the system Win key is
the Meta key and in the gnome-terminal only Alt key is
Hi!
After upgrade my Fedora from 32 to 33 I found Meta key in the
gnome-terminal works strange. Looks like now the gnome-terminal
recognizes Alt key as Meta key. Everywhere in the system Win key is
the Meta key and in the gnome-terminal only Alt key is the Meta key. I
see it because before Win
>
> On Mon, Aug 31, 2020 at 05:38:22PM +0200, Patrick Dupre wrote:
> >
> > echo $DISPLAY
> > :0
> >
> > ssh localhost
> > xmodmap: unable to open display ''
> > xmodmap: unable to open display ''
> >
> > xterm
> > xterm: Xt error: Can't open display:
> > xterm: DISPLAY is not set
>
> What abou
On Mon, Aug 31, 2020 at 05:38:22PM +0200, Patrick Dupre wrote:
>
> echo $DISPLAY
> :0
>
> ssh localhost
> xmodmap: unable to open display ''
> xmodmap: unable to open display ''
>
> xterm
> xterm: Xt error: Can't open display:
> xterm: DISPLAY is not set
What about running xterm on the local
local
> machines) without a -X or -Y ?
>
> if you want to verify it is a display setting/permission problem and
> not a gnome specific issue try "xterm" and see if it also says cannot
> open display and/or connection refused.
>
> On Mon, Aug 31, 2020 at 9:54 AM Patrick
d.
On Mon, Aug 31, 2020 at 9:54 AM Patrick Dupre wrote:
>
> Hello,
>
> When I lauch gnome-terminal, I get
>
> Maximum number of clients reachedUnable to init server: Could not connect:
> Connection refused
>
> # Failed to parse argumen
Hello,
When I lauch gnome-terminal, I get
Maximum number of clients reachedUnable to init server: Could not connect:
Connection refused
# Failed to parse arguments: Cannot open display:
Why that?
===
Patrick DUPRÉ
On 7/4/20 12:26 AM, Patrick Dupre wrote:
On 7/3/20 3:03 AM, Patrick Dupre wrote:
When I run
/usr/bin/gnome-terminal
I get:
# _g_io_module_get_default: Found default implementation local (GLocalVfs) for
‘gio-vfs’
# posix_spawn avoided (fd close requested)
# Error constructing proxy for
>
> On 7/3/20 3:03 AM, Patrick Dupre wrote:
> > When I run
> > /usr/bin/gnome-terminal
> >
> > I get:
> > # _g_io_module_get_default: Found default implementation local (GLocalVfs)
> > for ‘gio-vfs’
> > # posix_spawn avoided (fd clo
On 7/3/20 3:03 AM, Patrick Dupre wrote:
When I run
/usr/bin/gnome-terminal
I get:
# _g_io_module_get_default: Found default implementation local (GLocalVfs) for
‘gio-vfs’
# posix_spawn avoided (fd close requested)
# Error constructing proxy for org.gnome.Terminal:/org/gnome/Terminal/Factory0
real problem, except whe I run gnome-terminal,
> I always get:
> # _g_io_module_get_default: Found default implementation local (GLocalVfs)
> for ‘gio-vfs’
> # posix_spawn avoided (fd close requested)
> # _g_io_module_get_default: Found default implementation dconf
> (DConfSettings
arting gnome terminal will be a workaround, but you need to find out what makes dbus-update-activation-environment don't work here.
Can you tell me
systemctl --user enable dbus-broker.service
tell you if dbus-broker enabled(and running) or not?
systemctl --user enable dbus-bro
No real problem, except whe I run gnome-terminal,
I always get:
# _g_io_module_get_default: Found default implementation local (GLocalVfs) for ‘gio-vfs’
# posix_spawn avoided (fd close requested)
# _g_io_module_get_default: Found default implementation dconf (DConfSettingsBackend) for
dbus-broker instance is present.
>
> I think doing
> export $(dbus-launch)
> before starting gnome terminal will be a workaround, but you need to find
> out what makes dbus-update-activation-environment don't work here.
>
> Can you tell me
> systemctl --user enable dbus
That is where exact where the problem exact is. Do you get a failure state
from systemd status and unable to start that?
I think such things should be reported to bugzilla.
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an em
Seem that you are on x forwarding?
I think dbus-update-activation-environment should work here anyway, if a systemd-user and a dbus-broker instance is present.
I think doing
export $(dbus-launch)
before starting gnome terminal will be a workaround, but you need to find out what makes
Seem that you are on x forwarding?
I think dbus-update-activation-environment should work here anyway, if a
systemd-user and a dbus-broker instance is present.
I think doing
export $(dbus-launch)
before starting gnome terminal will be a workaround, but you need to find
out what makes dbus-update
Will
dbus-launch gnome-terminal
Work?
If that is not working, please describe your environment in details, I need more information.
it works, but
# _g_io_module_get_default: Found default implementation gvfs (GDaemonVfs) for ‘gio-vfs’
# _g_io_module_get_default: Found default
Will
dbus-launch gnome-terminal
Work?
If that is not working, please describe your environment in details, I need
more information.
Patrick Dupre 于 2020年7月3日周五 下午6:49写道：
>
>
> >
> > gnome-terminal needs dbus to start.
> > Do
> > dbus-update-activation-environm
>
> gnome-terminal needs dbus to start.
> Do
> dbus-update-activation-environment --all --systemd
> before exec gnome-terminal
> ___
dbus-update-activation-environment --all --systemd
dbus-update-activation-environment: error: unab
gnome-terminal needs dbus to start.
Do
dbus-update-activation-environment --all --systemd
before exec gnome-terminal
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code
Hello,
When I run
/usr/bin/gnome-terminal
I get:
# _g_io_module_get_default: Found default implementation local (GLocalVfs) for
‘gio-vfs’
# posix_spawn avoided (fd close requested)
# Error constructing proxy for org.gnome.Terminal:/org/gnome/Terminal/Factory0:
Failed to execute child process
On 6/25/19 5:19 AM, Patrick Dupre wrote:
I also get (in root)
# _g_io_module_get_default: Found default implementation local (GLocalVfs) for
‘gio-vfs’
# posix_spawn avoided (fd close requested)
# Error constructing proxy for org.gnome.Terminal:/org/gnome/Terminal/Factory0:
Failed to execute
On 6/25/19 2:22 AM, Patrick Dupre wrote:
Sent: Tuesday, June 25, 2019 at 8:50 AM
From: "Samuel Sieb"
To: users@lists.fedoraproject.org
Subject: Re: gnome-terminal issue
On 6/24/19 2:24 AM, Patrick Dupre wrote:
On one fedora 30 machine, when I run
/usr/bin/gnome-terminal, I get:
the
I also get (in root)
# _g_io_module_get_default: Found default implementation local (GLocalVfs) for
‘gio-vfs’
# posix_spawn avoided (fd close requested)
# Error constructing proxy for org.gnome.Terminal:/org/gnome/Terminal/Factory0:
Failed to execute child process “dbus-launch” (No such file or
> Sent: Tuesday, June 25, 2019 at 8:50 AM
> From: "Samuel Sieb"
> To: users@lists.fedoraproject.org
> Subject: Re: gnome-terminal issue
>
> On 6/24/19 2:24 AM, Patrick Dupre wrote:
> > On one fedora 30 machine, when I run
> > /usr/bin/gnome-te
On 6/24/19 2:24 AM, Patrick Dupre wrote:
On one fedora 30 machine, when I run
/usr/bin/gnome-terminal, I get:
the following message:
# _g_io_module_get_default: Found default implementation gvfs (GDaemonVfs) for
‘gio-vfs’
# _g_io_module_get_default: Found default implementation dconf
Hello,
On one fedora 30 machine, when I run
/usr/bin/gnome-terminal, I get:
the following message:
# _g_io_module_get_default: Found default implementation gvfs (GDaemonVfs) for
‘gio-vfs’
# _g_io_module_get_default: Found default implementation dconf
(DConfSettingsBackend) for ‘gsettings
Hello,
In FC30 (maybe it was the same in fc38), when we have a gnome-terminal
opened, we can easy open a new one just by clicking on +. However, if
the first terminal has been open owner preferences like
usr/bin/gnome-terminal --zoom=0.9 $*
when the 2nd terminal is opened, theses preferences are
I am trying to run gnome-terminal on openbox started from terminal
(multi-user.target) with startx command. GNOME applications that relies on DBus
can't communicate or fails to start in the case of gnome-terminal.
Starting gnome-terminal tries to pull gnome-terminal-server but that se
by underlining it.
But on the other hand something tmux related inhibits that contextual
menu.
You have probably turned on tmux' mouse support. Try
set mouse off
Not in a gnome-terminal, but with tmux in a sakura terminal, and mouse
switched on like this via ~/.tmux.conf:
setw -g mouse
On Thu, Apr 25, 2019 at 12:59 AM Markus Schönhaber
wrote:
>
> Chris Murphy, 24.4.2019 22:03 +0200:
>
> > If I run tmux, and in a tmux window/pane whatever, URLs are likewise
> > automatically underlined, and yet right-click does nothing. On the one
> > hand, Terminal clearly recognizes this is a l
Chris Murphy, 24.4.2019 22:03 +0200:
> If I run tmux, and in a tmux window/pane whatever, URLs are likewise
> automatically underlined, and yet right-click does nothing. On the one
> hand, Terminal clearly recognizes this is a link by underlining it.
> But on the other hand something tmux related
Hi,
If I'm in Gnome Terminal (no tmux), anytime I mouse over a URL it's
automatically underlined and I can right-click on it to get a
contextual menu with one of the options being to open the link.
Simple. Perfect.
If I run tmux, and in a tmux window/pane whatever, URLs ar
I had the same problem with F27->F28 upgrade. I solved thanks to your
suggestion.
Have a nice day
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
It seems that langpack-it was not updated/installed . Is solves also the
issue abour localization
Antonio Montagnani
Linux Fedora 28 Workstation
da/from Gmail
2018-05-02 7:56 GMT+02:00 Antonio M :
> after updating f27 to F28, I note that gnome-terminal doesn't start on my
> two sys
after updating f27 to F28, I note that gnome-terminal doesn't start on my
two systems. I had to install tilix to have a working terminal
Antonio Montagnani
Linux Fedora 27(Workstation)
da/from Gmail
___
users mailing list --
On Sun, Feb 18, 2018 at 5:04 AM, Joachim Backes
wrote:
>
> Anybody has seen that opening URL's found within the gnome-terminal output
> is not done correctly (popup menu: Open link ... in gnome-terminal)? Only
> the issuer's home URL is opened, independent from the URL f
On 02/18/18 18:04, Joachim Backes wrote:
> I'm running f27 under gnome with gnome-terminal as preferred terminal
> application.
>
> Anybody has seen that opening URL's found within the gnome-terminal output is
> not
> done correctly (popup menu: Open link ...
Hi all,
I'm running f27 under gnome with gnome-terminal as preferred terminal
application.
Anybody has seen that opening URL's found within the gnome-terminal
output is not done correctly (popup menu: Open link ... in
gnome-terminal)? Only the issuer's home URL is opened, i
I'm running f27 under gnome.
Anybody has seen that opening URL's found in the gnome-terminal output
is not done correctly? Only the issuers home URL is opened, independent
from the URL found in the terminal.
Using konsole5 instead of gnome-terminal solves the problem.
--
Fedora
On 12/05/2017 09:57 AM, Kevin Wilson wrote:
I am working with gnome-terminal under Fedora 27. I want to be able to
select text with the right click of a mouse, and to
paste it immediately when pressing the left button (not the middle
button). I am used to this with apps like putty, mRmoteNG and
Hello, Fedora users,
I am working with gnome-terminal under Fedora 27. I want to be able to
select text with the right click of a mouse, and to
paste it immediately when pressing the left button (not the middle
button). I am used to this with apps like putty, mRmoteNG and others
apps.
There was
On 09/17/2017 03:52 AM, Patrick Dupre wrote:
>
>> From: "Ed Greshko"
>> To: Fedora
>> Subject: Re: gnome-terminal
>>
>> On 09/17/17 17:30, Patrick Dupre wrote:
>>> When I run /usr/bin/gnome-terminal under fc26 (it was fine in fc24)
>>&g
:24 PM
> From: "Samuel Sieb"
> To: users@lists.fedoraproject.org
> Subject: Re: gnome-terminal
>
> On 09/17/2017 03:52 AM, Patrick Dupre wrote:
> > If I set DISPLAY properly
> > DISPLAY=:0
> > echo $?
> > 0
> > I get:
> > Invalid MIT-M
On 09/17/2017 03:52 AM, Patrick Dupre wrote:
If I set DISPLAY properly
DISPLAY=:0
echo $?
0
I get:
Invalid MIT-MAGIC-COOKIE-1 keyUnable to init server: Could not connect:
Connection refused
Failed to parse arguments: Cannot open display:
How about you provide some useful details about what you
> From: "Ed Greshko"
> To: Fedora
> Subject: Re: gnome-terminal
>
> On 09/17/17 17:30, Patrick Dupre wrote:
> > When I run /usr/bin/gnome-terminal under fc26 (it was fine in fc24)
> > from a gnome-terminal I get:
> >
> > Unable to init server: Co
On 09/17/17 17:30, Patrick Dupre wrote:
> When I run /usr/bin/gnome-terminal under fc26 (it was fine in fc24)
> from a gnome-terminal I get:
>
> Unable to init server: Could not connect: Connection refused
> Failed to parse arguments: Cannot open display:
>
> Can I avoid th
Hello,
When I run /usr/bin/gnome-terminal under fc26 (it was fine in fc24)
from a gnome-terminal I get:
Unable to init server: Could not connect: Connection refused
Failed to parse arguments: Cannot open display:
Can I avoid the error ?
Thank
On 08/19/2017 01:20 PM, Michael Schwendt wrote:
> On Sat, 19 Aug 2017 14:22:26 +0200, Joachim Backes wrote:
>
>> Hi guys,
>>
>> I'm running F26/x86_64 and having the following problem: In earlier
>> Fedora Versions, I could use PageUP or PageDown key to sc
On Sat, 19 Aug 2017 14:22:26 +0200, Joachim Backes wrote:
> Hi guys,
>
> I'm running F26/x86_64 and having the following problem: In earlier
> Fedora Versions, I could use PageUP or PageDown key to scroll through
> the gnome-terminal output (or I could use the mouse wheel f
Using mate-terminal instead of gnome-terminal runs as expected with the
PageUp/Page Down Key.
--
Fedora release 26 (Twenty Six)
Kernel-4.12.8-300.fc26.x86_64
Joachim Backes
https://www-user.rhrk.uni-kl.de/~backes/
___
users mailing list -- users
Joachim Backes writes:
On 08/19/17 14:32, Marmorstein, Robert wrote:
I'm running F26/x86_64 and having the following problem: In earlier
Fedora Versions, I could use PageUP or PageDown key to scroll through
the gnome-terminal output (or I could use the mouse wheel for doing
Does
On 08/19/2017 08:36 PM, Joachim Backes wrote:
> On 08/19/17 14:22, Joachim Backes wrote:
>> Hi guys,
>>
>> I'm running F26/x86_64 and having the following problem: In earlier
>> Fedora Versions, I could use PageUP or PageDown key to scroll through
>> the gno
On 08/19/17 14:32, Marmorstein, Robert wrote:
I'm running F26/x86_64 and having the following problem: In earlier
Fedora Versions, I could use PageUP or PageDown key to scroll through
the gnome-terminal output (or I could use the mouse wheel for doing
Does SHIFT-PageUp work?
Robert
On 08/19/17 14:22, Joachim Backes wrote:
Hi guys,
I'm running F26/x86_64 and having the following problem: In earlier
Fedora Versions, I could use PageUP or PageDown key to scroll through
the gnome-terminal output (or I could use the mouse wheel for doing the
same). But in F26, nothings ha
>I'm running F26/x86_64 and having the following problem: In earlier
>Fedora Versions, I could use PageUP or PageDown key to scroll through
>the gnome-terminal output (or I could use the mouse wheel for doing
Does SHIFT-PageUp work?
Robert
___
Hi guys,
I'm running F26/x86_64 and having the following problem: In earlier
Fedora Versions, I could use PageUP or PageDown key to scroll through
the gnome-terminal output (or I could use the mouse wheel for doing the
same). But in F26, nothings happens if I use these keys or the
Seems that doing
dnf install langpacks-en
gets rid of the locale issues. Not sure why the system upgrade doesn't
install a langpack.
On Mon, Jul 17, 2017 at 6:17 PM, Mike Zingale wrote:
> I just did an update from F25 to F26 via dnf. After it boots, I can no
> longer start gno
I just did an update from F25 to F26 via dnf. After it boots, I can no
longer start gnome terminal (nothing shows). If I ssh into the machine and
try it remotely, I see the following:
$ gnome-terminal
(process:3586): Gtk-WARNING **: Locale not supported by C library.
Using the fallback &#
On Fri, Nov 04, 2016 at 09:06:12PM -0400, Michael B Allen wrote:
> Hi Matthew,
> I can confirm roxterm works with vi as enternal editor in Sylpheed:
> roxterm -e vi '%s'
> For some reason it opens very small but that is a wart that I can live
> with for now.
Noticed that too -- probaby worth fil
g _other_ than the process
> termination.
>
>> I know gnome-terminal is "special" so perhaps there is another
>> terminal for Fedora?
>
> You may be able to use mate-terminal; I think it'll retain the old
> behavior, although I haven't tried it. If t
On Fri, Nov 04, 2016 at 05:34:32PM -0400, Michael B Allen wrote:
> Does anyone have a recommended work-around?
AFAIK the only workaround would be in the program itself -- it would
have to know to wait for something _other_ than the process
termination.
> I know gnome-terminal is "
I have been using this external editor command for the Sylpheed mailer:
gnome-terminal --disable-factory -x vim '%s'
This allows launching a terminal with vi so that I can capture shell
command output, edit things with vi and insert files and such. This is
a very powerful and importa
Machine lost power and upon restoration and restart, the login screen
shows "Terminal 1 new notification" though, of course, terminal did
not survive the interuption.
How can I reset that notice? It continues to appear each time I'm back
at the login screen.
--
Ted Roche
Ted Roche & Associates,
On Mon, 21 Sep 2015 18:43:29 -0400
Tom Horsley wrote:
> The complicated solution...
Actually, there is also another solution, run the command
inside-out like so:
gnome-terminal -e "ssh -X remotesystem"
That way you make gnome-terminal happy by using the
local dbus session and y
The simplest solution is to ssh -X xterm instead of gnome-terminal
since xterm doesn't desperately need to talk dbus like every
gnome application.
The complicated solution is to run a script rather than
a simple gnome-terminal command and have the script
do something like:
#!/bin/bash
On Sep 21, 2015 4:59 PM, "Patrick Dupre" wrote:
>
> Hello,
>
> In fc22 (in fc20 it was OK, if I remember correctly), when I login
> with ssh -X and then on the server, I run gnome-terminal, I get:
> ** (gnome-terminal:2515): WARNING **: Couldn't connect to access
> On 09/21/2015 02:58 PM, Patrick Dupre wrote:
> > Hello,
> >
> > In fc22 (in fc20 it was OK, if I remember correctly), when I login
> > with ssh -X and then on the server, I run gnome-terminal, I get:
> > ** (gnome-terminal:2515): WARNING **: Couldn't connec
On 09/21/2015 02:58 PM, Patrick Dupre wrote:
Hello,
In fc22 (in fc20 it was OK, if I remember correctly), when I login
with ssh -X and then on the server, I run gnome-terminal, I get:
** (gnome-terminal:2515): WARNING **: Couldn't connect to accessibility bus:
Failed to connect to socket
Hello,
In fc22 (in fc20 it was OK, if I remember correctly), when I login
with ssh -X and then on the server, I run gnome-terminal, I get:
** (gnome-terminal:2515): WARNING **: Couldn't connect to accessibility bus:
Failed to connect to socket /tmp/dbus-N20xllktmP: Connection refused
I r
On Mon, Sep 21, 2015 at 12:18:17PM +0200, Patrick Dupre wrote:
> How can I change the preference either manually from a text window
> or from gnome ?
Run the dconf-editor and look under org → gnome → terminal.
--
Matthew Miller
Fedora Project Leader
--
users mailing list
Hello,
I was not satisfied by the behavior of gnome-terminal.
Then I checked
run my own command (or something similar) in preferences (of gnome-terminal).
Then it became crazy, opening multiple gnome-terminals.
I cannot access to the preferences any more.
I can only kill gnome-terminal from a
Thank,
>
> On 08/12/15 10:28, Patrick Dupre wrote:
> > Hello,
> >
> > it seems than in fedora 22, the color coding for vi has changed.
> > How can I get the previous mapping or have control on the
> > new coding?
>
> i do not have fedora 22 up, but for centos 6.6, i have a directory;
>
>/u
l vim, you should make sure that gnome terminal is set to
be a 256 color terminal and that the color scheme is built for terminal use.
On Wed, 12 Aug 2015 11:28:00 -0400 Patrick Dupre<pdu...@gmx.com>
wrote
Hello,
it seems than in fedora 22, the color coding for vi has changed.
H
On 08/12/15 10:28, Patrick Dupre wrote:
> Hello,
>
> it seems than in fedora 22, the color coding for vi has changed.
> How can I get the previous mapping or have control on the
> new coding?
i do not have fedora 22 up, but for centos 6.6, i have a directory;
/usr/share/vim/vim72/colors
wit
Hello,
it seems than in fedora 22, the color coding for vi has changed.
How can I get the previous mapping or have control on the
new coding?
Thank
===
Patrick DUPRÉ | | email: pdu...@gmx.com
Il giorno dom, 28/06/2015 alle 18.34 +0200, Ahmad Samir ha scritto:
> gnome-terminal had an option like that in F21 but it was removed in
> recent releases
For my curiosity, could someone explain me why this useful feature was
removed a few versions ago?
And now, which was decided to rest
On 28 June 2015 at 17:47, Joachim Backes wrote:
> Hi all,
>
> I'm running f22 with MATE desktop and GNOME3 desktop. I'm seeing
> different strategies selecting text in gnome-terminal and mate-terminal:
>
> Suppose there is a line containing the text
> "sy-2
Hi all,
I'm running f22 with MATE desktop and GNOME3 desktop. I'm seeing
different strategies selecting text in gnome-terminal and mate-terminal:
Suppose there is a line containing the text
"sy-2015-06-13_08:21:23-4.0.5-300-F22" in both terminals. Double
clicking in the g
On 06/15/2015 10:48 AM, Ahmad Samir wrote:
>From this gnome bug report[1], you can modify that setting using a
command like this, as user:
$ dconf write
/org/gnome/terminal/legacy/profiles:/:${Profile_ID}/word-char-exceptions
'@ms "-,.;/?%&#_=+@~·:"'
I added : at
On 15 June 2015 at 15:48, Stephen Berg (Contractor)
wrote:
> After reinstalling with F22 a double click in gnome-terminal is behaving
> differently.
>
> Before if I double clicked on an NFS share such as "servername:/export/data"
> the entire string would be selected.
After reinstalling with F22 a double click in gnome-terminal is behaving
differently.
Before if I double clicked on an NFS share such as
"servername:/export/data" the entire string would be selected.
After the reinstall I only get "servername" or "/export/data&quo
Hi,
I've just installed f20 and can't figure out why the gnome-terminal
scroll history doesn't work. I've enabled both "scroll on output" and
"scroll on keystroke" in the Scrolling tab, but there is still no
scroll history.
What am I missing?
T
On Mon, Dec 30, 2013 at 1:08 AM, Robert Moskowitz wrote:
> On 12/29/2013 05:04 PM, Tom H wrote:
>> On Sun, Dec 29, 2013 at 3:57 PM, Robert Moskowitz
>> wrote:
>>>
>>> Oh, and I have lost to lock my desktop.
>>
>> super-l
>
> Got it thanks.
>
> I only started seeing reference to the 'super' key w
Allegedly, on or about 29 December 2013, Robert Moskowitz sent:
> it sure seems like at first install, was working,
> but could have just been another of those senior moments.
For several years, through different incarnations of Fedora, and on
different hardware, I've had computers where the lo
On 12/29/2013 08:08 PM, Robert Moskowitz wrote:
On 12/29/2013 05:04 PM, Tom H wrote:
On Sun, Dec 29, 2013 at 3:57 PM, Robert Moskowitz
wrote:
Oh, and I have lost to lock my desktop.
super-l
Got it thanks.
I only started seeing reference to the 'super' key with f20. Seems I
was blissfull
On 12/29/2013 05:04 PM, Tom H wrote:
On Sun, Dec 29, 2013 at 3:57 PM, Robert Moskowitz wrote:
Oh, and I have lost to lock my desktop.
super-l
Got it thanks.
I only started seeing reference to the 'super' key with f20. Seems I
was blissfully ignorant until recently what to call that butto
On Sun, Dec 29, 2013 at 3:57 PM, Robert Moskowitz wrote:
>
> Oh, and I have lost to lock my desktop.
super-l
--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Fedora Code of Conduct: http://f
/share/applications/gnome-terminal.desktop ~/Desktop
Then install and run "gnome-tweak-tool" package:
yum -y install gnome-tweak-tool
When using GNOME Shell, run gnome-tweak-tool, enable "Icons on Desktop".
Double-click the gnome-terminal icon on desktop to start a terminal
Michael Schwendt writes:
It may not even be a bug in Nautilus either, since other components take
care of stopping/starting it (e.g. gnome-tweak-tool and gnome-shell).
What happens if you kill all "nautilus" processes, then start a terminal
(e.g. gnome-terminal) in a way that it
inal.desktop ~/Desktop
Then install and run "gnome-tweak-tool" package:
yum -y install gnome-tweak-tool
When using GNOME Shell, run gnome-tweak-tool, enable "Icons on Desktop".
Double-click the gnome-terminal icon on desktop to start a terminal.
After a reboot (at least her
On 12/29/2013 03:00 AM, Ed Greshko wrote:
The thread with the subject of "gnome-terminal in F20 defaults to / for the initial
directory" prompted me to do some testing and I've found an oddity.
The desktop file is as follows...
[egreshko@f20f ]$ cat Desktop/gnome-terminal.de
The thread with the subject of "gnome-terminal in F20 defaults to / for the
initial directory" prompted me to do some testing and I've found an oddity.
The desktop file is as follows...
[egreshko@f20f ]$ cat Desktop/gnome-terminal.desktop
[Desktop Entry]
Comment[en_US]=
Comment
uence runtime
behaviour, too.
It may not even be a bug in Nautilus either, since other components take
care of stopping/starting it (e.g. gnome-tweak-tool and gnome-shell).
What happens if you kill all "nautilus" processes, then start a terminal
(e.g. gnome-terminal) in a way that it s
On 12/28/13 22:28, Sam Varshavchik wrote:
> Michael Schwendt writes:
>
>> On Fri, 27 Dec 2013 21:47:56 -0500, Sam Varshavchik wrote:
>>
>> > Previously, experimentation showed that gnome-terminal spawns a shell with
>> > the current directory inherited from
1 - 100 of 204 matches
Mail list logo
