Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.os.linux.advocacy > #240025 > unrolled thread
| Started by | Lusotec <nomail@nomail.not> |
|---|---|
| First post | 2014-04-24 19:52 +0100 |
| Last post | 2014-04-24 15:32 -0600 |
| Articles | 6 on this page of 26 — 13 participants |
Back to article view | Back to comp.os.linux.advocacy
This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by
below is the oldest one visible, not the original post.
Re: Marti van Lin: "Ubuntu 14.04 LTS will be rock solid" Lusotec <nomail@nomail.not> - 2014-04-24 19:52 +0100
Re: Marti van Lin: "Ubuntu 14.04 LTS will be rock solid" Peter Köhlmann <peter-koehlmann@t-online.de> - 2014-04-24 20:57 +0200
Re: Marti van Lin: "Ubuntu 14.04 LTS will be rock solid" Lusotec <nomail@nomail.not> - 2014-04-24 21:36 +0100
Re: Marti van Lin: "Ubuntu 14.04 LTS will be rock solid" Peter Köhlmann <peter-koehlmann@t-online.de> - 2014-04-24 22:52 +0200
Re: Marti van Lin: "Ubuntu 14.04 LTS will be rock solid" Snit <usenet@gallopinginsanity.com> - 2014-04-24 17:05 -0700
Re: Marti van Lin: "Ubuntu 14.04 LTS will be rock solid" chrisv <chrisv@nospam.invalid> - 2014-04-25 06:48 -0500
Re: Marti van Lin: "Ubuntu 14.04 LTS will be rock solid" chrisv <chrisv@nospam.invalid> - 2014-04-25 07:03 -0500
Re: Marti van Lin: "Ubuntu 14.04 LTS will be rock solid" DFS <nospam@dfs.com> - 2014-04-25 08:51 -0400
Re: Marti van Lin: "Ubuntu 14.04 LTS will be rock solid" flatfish+++ <phlatphish@yahoo.com> - 2014-04-25 09:20 -0400
Re: Marti van Lin: "Ubuntu 14.04 LTS will be rock solid" DFS <nospam@dfs.com> - 2014-04-25 11:13 -0400
Re: Marti van Lin: "Ubuntu 14.04 LTS will be rock solid" flatfish+++ <phlatphish@yahoo.com> - 2014-04-25 11:20 -0400
Re: Marti van Lin: "Ubuntu 14.04 LTS will be rock solid" GreyCloud <mist@cumulus.com> - 2014-04-25 11:40 -0600
Re: Marti van Lin: "Ubuntu 14.04 LTS will be rock solid" flatfish+++ <phlatphish@yahoo.com> - 2014-04-25 14:21 -0400
Re: Marti van Lin: "Ubuntu 14.04 LTS will be rock solid" GreyCloud <mist@cumulus.com> - 2014-04-25 12:57 -0600
Is it hard to change xterm's font ? Jeff-Relf.Me <@.> - 2014-04-25 16:50 -0700
Re: Is it hard to change xterm's font ? Silver Slimer <slvrslmr@lv.c> - 2014-04-25 21:19 -0400
Re: Is it hard to change xterm's font ? DFS <nospam@dfs.com> - 2014-04-27 17:45 -0400
Re: Is it hard to change xterm's font ? Hadron<hadronquark@gmail.com> - 2014-04-28 15:53 +0200
Re: Is it hard to change xterm's font ? TomB <tommy.bongaerts@gmail.com> - 2014-05-01 23:06 +0000
Re: Is it hard to change xterm's font ? Chris Ahlstrom <OFeem1987@teleworm.us> - 2014-05-01 19:55 -0400
Re: Is it hard to change xterm's font ? flatfish+++ <phlatphish@yahoo.com> - 2014-05-02 07:46 -0400
Re: Is it hard to change xterm's font ? Hadron<hadronquark@gmail.com> - 2014-05-02 15:03 +0200
Re: Is it hard to change xterm's font ? flatfish+++ <phlatphish@yahoo.com> - 2014-05-02 09:21 -0400
Re: Is it hard to change xterm's font ? Steve Carroll <fretwizzen@gmail.com> - 2014-05-02 11:22 -0700
Re: Is it hard to change xterm's font ? DFS <nospam@dfs.com> - 2014-05-02 13:00 -0400
Re: Marti van Lin: "Ubuntu 14.04 LTS will be rock solid" GreyCloud <mist@cumulus.com> - 2014-04-24 15:32 -0600
Page 2 of 2 — ← Prev page 1 [2]
| From | flatfish+++ <phlatphish@yahoo.com> |
|---|---|
| Date | 2014-05-02 07:46 -0400 |
| Subject | Re: Is it hard to change xterm's font ? |
| Message-ID | <1xl0t1wxmfu7g.1fr6vy80rtrzh.dlg@40tude.net> |
| In reply to | #241174 |
On Thu, 1 May 2014 19:55:00 -0400, Chris Ahlstrom wrote: > TomB wrote this copyrighted missive and expects royalties: > >> On 2014-04-27, the following emerged from the brain of DFS: > > He has a brain? Get outa town! > >>> On 04/25/2014 07:50 PM, Jeff-Relf.Me wrote: >>>> DFS, Is it hard to change xterm's font ? >>> >>> Not hard - but to change it permanently you have to Google for the exact >>> string, then create or edit the ~/.Xresources file. >> >> % man xterm would do the trick too > > Or ~/.Xdefaults. > > It is no harder than editing the Registry. Yea, but with Windows you don't have to edit the Registry to change the fonts in a command prompt. Nice self nuke Chris Ahlstrom. -- flatfish+++ 163 Reasons not to deal with Michael "Snit" Glasser, the Prescott Computer Guy http://cosmicpenguin.com/snitlist.html
[toc] | [prev] | [next] | [standalone]
| From | Hadron<hadronquark@gmail.com> |
|---|---|
| Date | 2014-05-02 15:03 +0200 |
| Subject | Re: Is it hard to change xterm's font ? |
| Message-ID | <87ha585o4h.fsf@gmail.com> |
| In reply to | #241202 |
flatfish+++ <phlatphish@yahoo.com> writes: > On Thu, 1 May 2014 19:55:00 -0400, Chris Ahlstrom wrote: > >> TomB wrote this copyrighted missive and expects royalties: >> >>> On 2014-04-27, the following emerged from the brain of DFS: >> >> He has a brain? Get outa town! >> >>>> On 04/25/2014 07:50 PM, Jeff-Relf.Me wrote: >>>>> DFS, Is it hard to change xterm's font ? >>>> >>>> Not hard - but to change it permanently you have to Google for the exact >>>> string, then create or edit the ~/.Xresources file. >>> >>> % man xterm would do the trick too >> >> Or ~/.Xdefaults. >> >> It is no harder than editing the Registry. > > Yea, but with Windows you don't have to edit the Registry to change > the fonts in a command prompt. > > Nice self nuke Chris Ahlstrom. He really is a serious fucking idiot at times. Plus he forgot the xrdb merge.... Then you have the issues with case and actually finding the documented x resources an app uses. eg http://askubuntu.com/questions/389633/xrdb-merge-xresources-disables-gtk-anti-aliasing -- "I have a BSEE.... Negative feedback has many benefits, but "maintaining stability" is not one of them. Just the opposite, in fact." The turdv/chrisv idiot and his pretend BSEE degree. PLEASE VISIT OUR HALL OF LINUX IDIOTS http://linuxidiots.blogspot.com/
[toc] | [prev] | [next] | [standalone]
| From | flatfish+++ <phlatphish@yahoo.com> |
|---|---|
| Date | 2014-05-02 09:21 -0400 |
| Subject | Re: Is it hard to change xterm's font ? |
| Message-ID | <x2gpoiy71dek$.184gplxna258f.dlg@40tude.net> |
| In reply to | #241219 |
On Fri, 02 May 2014 15:03:26 +0200, Hadron wrote: > flatfish+++ <phlatphish@yahoo.com> writes: > >> On Thu, 1 May 2014 19:55:00 -0400, Chris Ahlstrom wrote: >> >>> TomB wrote this copyrighted missive and expects royalties: >>> >>>> On 2014-04-27, the following emerged from the brain of DFS: >>> >>> He has a brain? Get outa town! >>> >>>>> On 04/25/2014 07:50 PM, Jeff-Relf.Me wrote: >>>>>> DFS, Is it hard to change xterm's font ? >>>>> >>>>> Not hard - but to change it permanently you have to Google for the exact >>>>> string, then create or edit the ~/.Xresources file. >>>> >>>> % man xterm would do the trick too >>> >>> Or ~/.Xdefaults. >>> >>> It is no harder than editing the Registry. >> >> Yea, but with Windows you don't have to edit the Registry to change >> the fonts in a command prompt. >> >> Nice self nuke Chris Ahlstrom. > > He really is a serious fucking idiot at times. > > Plus he forgot the xrdb merge.... > > Then you have the issues with case and actually finding the documented x > resources an app uses. > > eg > http://askubuntu.com/questions/389633/xrdb-merge-xresources-disables-gtk-anti-aliasing Average user doesn't stand a chance of finding that. -- flatfish+++ 163 Reasons not to deal with Michael "Snit" Glasser, the Prescott Computer Guy http://cosmicpenguin.com/snitlist.html
[toc] | [prev] | [next] | [standalone]
| From | Steve Carroll <fretwizzen@gmail.com> |
|---|---|
| Date | 2014-05-02 11:22 -0700 |
| Subject | Re: Is it hard to change xterm's font ? |
| Message-ID | <63a39d1b-8fe1-4bbc-be3b-27fbc7a28c14@googlegroups.com> |
| In reply to | #241219 |
On Friday, May 2, 2014 1:03:26 PM UTC, Hadron wrote: > flatfish+++ <phlatphish@yahoo.com> writes: > > > > > On Thu, 1 May 2014 19:55:00 -0400, Chris Ahlstrom wrote: > > > > > >> TomB wrote this copyrighted missive and expects royalties: > > >> > > >>> On 2014-04-27, the following emerged from the brain of DFS: > > >> > > >> He has a brain? Get outa town! > > >> > > >>>> On 04/25/2014 07:50 PM, Jeff-Relf.Me wrote: > > >>>>> DFS, Is it hard to change xterm's font ? > > >>>> > > >>>> Not hard - but to change it permanently you have to Google for the exact > > >>>> string, then create or edit the ~/.Xresources file. > > >>> > > >>> % man xterm would do the trick too > > >> > > >> Or ~/.Xdefaults. > > >> > > >> It is no harder than editing the Registry. > > > > > > Yea, but with Windows you don't have to edit the Registry to change > > > the fonts in a command prompt. > > > > > > Nice self nuke Chris Ahlstrom. > > > > He really is a serious fucking idiot at times. > > > > Plus he forgot the xrdb merge.... > > > > Then you have the issues with case and actually finding the documented x > > resources an app uses. > > > > eg > > http://askubuntu.com/questions/389633/xrdb-merge-xresources-disables-gtk-anti-aliasing > > > > > > -- > > "I have a BSEE.... Negative feedback has many benefits, but "maintaining stability" is not one of them. Just the opposite, in fact." > > The turdv/chrisv idiot and his pretend BSEE degree. > > PLEASE VISIT OUR HALL OF LINUX IDIOTS > > http://linuxidiots.blogspot.com/ Another thread ruined by Michael Glasser Prescott Computer guy of Prescott, Arizona. http://prescottcomputerguy.com His video expertise is shown here http://prescottcomputerguy.com/screenflow
[toc] | [prev] | [next] | [standalone]
| From | DFS <nospam@dfs.com> |
|---|---|
| Date | 2014-05-02 13:00 -0400 |
| Subject | Re: Is it hard to change xterm's font ? |
| Message-ID | <lk0iuk$nb6$1@dont-email.me> |
| In reply to | #241174 |
On 05/01/2014 07:55 PM, Chris Ahlstrom wrote:
> TomB wrote this copyrighted missive and expects royalties:
>
>> On 2014-04-27, the following emerged from the brain of DFS:
>
> He has a brain? Get outa town!
>
>>> On 04/25/2014 07:50 PM, Jeff-Relf.Me wrote:
>>>> DFS, Is it hard to change xterm's font ?
>>>
>>> Not hard - but to change it permanently you have to Google for the exact
>>> string, then create or edit the ~/.Xresources file.
>>
>> % man xterm would do the trick too
>
> Or ~/.Xdefaults.
>
> It is no harder than editing the Registry.
It's probably easier, if you know where to find the file in the first
place. (figuring out where it is takes experience or Googling)
And the text file usually makes more sense, whereas many Windows
Registry entries are unreadable.
In the real world, though, Registry editing for Windows config is
extremely rare, whereas text file editing for Linux config is extremely
common.
> Of course, you could also use terminals like Roxterm, Gnome-terminal, or
> XFce4-terminal, which have "GUIs" for configuration of the terminal.
xterm apparently has "GUI" menus and toolbars:
−tb
This option, corresponding to the toolBar resource, indicates that xterm
should display a toolbar (or menubar) at the top of its window. The
buttons in the toolbar correspond to the popup menus, e.g.,
control/left/mouse for “Main Options”.
+tb
This option indicates that xterm should not set up a toolbar.
http://invisible-island.net/xterm/manpage/xterm.html
but when you try
# xterm -tb
# xterm +tb
it throws errors: xterm: bad command line option "-tb"
======================================================================
[dfs@manjaro LearnCTheHardWay]# xterm -help
XTerm(303) usage:
xterm [-options ...] [-e command args]
where options include:
-/+132 turn on/off 80/132 column switching
-C intercept console messages
-Sccn slave mode on "ttycc", file descriptor "n"
-T string title name for window
-/+ah turn on/off always highlight
-/+ai turn off/on active icon
-/+aw turn on/off auto wraparound
-b number internal border in pixels
-/+bc turn on/off text cursor blinking
-bcf milliseconds time text cursor is off when blinking
-bcn milliseconds time text cursor is on when blinking
-bd color border color
-/+bdc turn off/on display of bold as color
-bg color background color
-bw number border width in pixels
-/+cb turn on/off cut-to-beginning-of-line
inhibit
-cc classrange specify additional character classes
-/+cjk_width turn on/off legacy CJK width convention
-class string class string (XTerm)
-/+cm turn off/on ANSI color mode
-/+cn turn on/off cut newline inhibit
-cr color text cursor color
-/+cu turn on/off curses emulation
-/+dc turn off/on dynamic color selection
-display displayname X server to contact
-e command args ... command to execute
-fa pattern FreeType font-selection pattern
-fb fontname bold text font
-/+fbb turn on/off normal/bold font
comparison inhibit
-/+fbx turn off/on linedrawing characters
-fd pattern FreeType Doublesize font-selection pattern
-fg color foreground color
-fi fontname icon font for active icon
-fn fontname normal text font
-fs size FreeType font-size
-/+fullscreen turn on/off fullscreen on startup
-fw fontname doublewidth text font
-fwb fontname doublewidth bold text font
-fx fontname XIM fontset
%geom Tek window geometry
#geom icon window geometry
-geometry geom size (in characters) and position
-help print out this message
-/+hm turn on/off selection-color override
-/+hold turn on/off logic that retains window
after exit
-iconic start iconic
-/+ie turn on/off initialization of 'erase'
from pty
-/+im use insert mode for TERMCAP
-into windowId use the window id given to -into as
the parent window rather than the default root window
-/+j turn on/off jump scroll
-/+k8 turn on/off C1-printable classification
-kt keyboardtype set keyboard type: tcap sun vt220
-/+l turn on/off logging
-/+lc turn on/off locale mode using luit
-lcc path filename of locale converter
(/usr/bin/luit)
-leftbar force scrollbar left
-lf filename logging filename
-/+ls turn on/off login shell
-/+maximized turn on/off maxmize on startup
-/+mb turn on/off margin bell
-mc milliseconds multiclick time in milliseconds
-/+mesg forbid/allow messages
-/+mk_width turn on/off simple width convention
-ms color pointer color
-n string icon name for window
-name string client instance, icon, and title strings
-nb number margin bell in characters from right end
-/+nul turn off/on display of underlining
-/+pc turn on/off PC-style bold colors
-/+pob turn on/off pop on bell
-report-colors report colors as they are allocated
-report-fonts report fonts as loaded to stdout
-rightbar force scrollbar right (default left)
-/+rv turn on/off reverse video
-/+rvc turn off/on display of reverse as color
-/+rw turn on/off reverse wraparound
-/+s turn on/off multiscroll
-/+samename turn on/off the no-flicker option for
title and icon name
-/+sb turn on/off scrollbar
-selbg color selection background color
-selfg color selection foreground color
-/+sf turn on/off Sun Function Key escape codes
-/+si turn on/off scroll-on-tty-output inhibit
-/+sk turn on/off scroll-on-keypress
-sl number number of scrolled lines to save
-/+sm turn on/off the session-management support
-/+sp turn on/off Sun/PC Function/Keypad mapping
-/+t turn on/off Tek emulation window
-ti termid terminal identifier
-title string title string
-tm string terminal mode keywords and characters
-tn name TERM environment variable name
-/+u8 turn on/off UTF-8 mode (implies
wide-characters)
-/+uc turn on/off underline cursor
-/+ulc turn off/on display of underline as color
-/+ulit turn off/on display of underline as
italics
-/+ut turn on/off utmp support
-/+vb turn on/off visual bell
-version print the version number
-/+wc turn on/off wide-character mode
-/+wf turn on/off wait for map before
command exec
-xrm resourcestring additional resource specifications
-ziconbeep percent beep and flag icon of window having
hidden output
Fonts should be fixed width and, if both normal and bold are specified,
should
have the same size. If only a normal font is specified, it will be used for
both normal and bold text (by doing overstriking). The -e option, if given,
must appear at the end of the command line, otherwise the user's default
shell
will be started. Options that start with a plus sign (+) restore the
default.
======================================================================
[toc] | [prev] | [next] | [standalone]
| From | GreyCloud <mist@cumulus.com> |
|---|---|
| Date | 2014-04-24 15:32 -0600 |
| Message-ID | <wZ-dnZtDGqptH8TOnZ2dnUVZ_vidnZ2d@bresnan.com> |
| In reply to | #240025 |
On 4/24/2014 12:52 PM, Lusotec wrote: > GreyCloud wrote: >> From another group a fellow did say that UNIX doesn't allow for more >> than 2 rings... how that is I don't know. >> And I'm not sure if Linux falls into that same category. > > I have only read some parts of the UNIX specs, so I may be wrong, but I > would bet UNIX specs make no mention of rings (or similar) at all. More likely due to legacy code and costs. I still have the OpenGroup UNIX specs, but it is rather lengthy read. Most of it always says "optional". The one spec I did find was the wording "shall" in regards to the C compiler and an ISO number. This is where Apple fell short now in dumping gcc and going for llvm compiler. Which means Apple OS X is no longer legitimately a UNIX anymore.
[toc] | [prev] | [standalone]
Page 2 of 2 — ← Prev page 1 [2]
Back to top | Article view | comp.os.linux.advocacy
csiph-web