Add an option to disable the emoticon-emoji auto-conversion?

ruby R53

ruby R53

I often forget about this little detail when posting here. I sometimes do mean to use an emoji, other times I just want an emoticon instead.
But then, for some reason, the system just converts it to an emoji without even telling me, so I end up accidentally typing an emoji, and have to edit my post by adding a space between the eyes and mouth. Kinda awkward.

Also, shit like this happen thanks to that:
1762619872556.png
 
That's why you should put system output, configuration files, etc. inside a [code]...[/code] block. First it'll look nicer because it will use a monospaced font, and second it'll prevent the forum software from trying to interpret emoticons, URLs and whatnot.

wblock@

Thread 'Formatting Guidelines'

1. Please write as clearly as possible. Use English punctuation and capitalization, and avoid abbreviating things. This helps to improve the clarity of messages and make problems easier to solve.

2. Use BBCode formatting tags. As with punctuation, these tags make messages easier to read. For example, using the [cmd] tag on commands shows exactly which characters are part of the command. Here are the special BBCode tags we have added:

[file] for file and directory names: [file]/etc/rc.conf[/file] shows /etc/rc.conf​

[cmd] for commands...​
  • Thanks
  • Like

Example:
Code: 
dice@fbsd-test:~ % dmesg
---<<BOOT>>---
Copyright (c) 1992-2023 The FreeBSD Project.
Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994
        The Regents of the University of California. All rights reserved.
FreeBSD is a registered trademark of The FreeBSD Foundation.
FreeBSD 14.3-RELEASE-p3 GENERIC amd64
FreeBSD clang version 19.1.7 (https://github.com/llvm/llvm-project.git llvmorg-19.1.7-0-gcd708029e0b2)
SRAT: Ignoring memory at addr 0xff000000
VT: init without driver.
CPU: Intel(R) Xeon(R) CPU           E5620  @ 2.40GHz (2400.21-MHz K8-class CPU)
  Origin="GenuineIntel"  Id=0x206c2  Family=0x6  Model=0x2c  Stepping=2
  Features=0x9f83fbff<FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,MMX,FXSR,SSE,SSE2,SS,HTT,PBE>
  Features2=0x829e6217<SSE3,PCLMULQDQ,DTES64,DS_CPL,SSSE3,CX16,xTPR,PCID,DCA,SSE4.1,SSE4.2,POPCNT,AESNI,HV>
  AMD Features=0x2c100800<SYSCALL,NX,Page1GB,RDTSCP,LM>
  AMD Features2=0x1<LAHF>
  TSC: P-state invariant
Hypervisor: Origin = "bhyve bhyve "
real memory  = 5368709120 (5120 MB)
avail memory = 4099350528 (3909 MB)
Event timer "LAPIC" quality 600
ACPI APIC Table: <BHYVE  BVAPIC >
FreeBSD/SMP: Multiprocessor System Detected: 2 CPUs
FreeBSD/SMP: 2 package(s) x 1 core(s)
random: unblocking device.
ioapic0 <Version 1.1> irqs 0-31
Launching APs: 1
random: entropy device external interface
kbd1 at kbdmux0
 
BBCode [code] is popular on forums, but I run into all sorts of ways to format a code box :p (Reddit is ` or 4-spaces, DokuWiki '' (2 apostrophes/not a double quote") or <code>, Discourse 3 ```)

Probably the first time I've legit-used [NOPARSE] too :p
 
yeah i wish this forum used markdown for formatting instead, much much better in my opinion
or had an option to switch between markdown and whatever the hell this formatting thing is called, just like how Reddit does

bbcode is fine but kinda ugly in my opinion

eternal_noob said:
According to History of WYSIWYG and CMS: a timeline, users have been able to find out about this since 1991.
Click to expand...
notice how you said "have been able to"? xp
 
ruby R53 said:
not that many users will be aware of that
Click to expand...
It's "REQUIRED READING", you get pointed to it when you sign up. It's plastered all over. When I edit posts (which I have to do a LOT) I point to the formatting guidelines. But it's the same as license agreements, very few people read them and even less actually understand how it works. There's a bunch of users that have been here for years and still don't properly format their posts.

forums.freebsd.org

Forum Rules and Guidelines (REQUIRED READING)

This forum contains the Rules and Guidelines governing the FreeBSD Forums.
forums.freebsd.org forums.freebsd.org
 
SirDice said:
There's a bunch of users that have been here for years and still don't properly format their posts.
Click to expand...
Assuming I'm not the only one seeing this (in Firefox), still many of of the editors options break the line.

One gets tired of constantly correcting them or having to manually set the BBCode, which is time-consuming.

Original: testing the <option> option, and after applying from the editor.
Code: 
testing the
[HIGHLIGHT]Highlight[/HIGHLIGHT]
 option

testing the
[CMD]Command[/CMD]
 option

testing the
[FILE]Filenam[/FILE]
 option

testing the
[PORT]Port Program[/PORT]
 option

testing the
[MAN]Manual Page[/MAN]
 option

testing the
[PMAN]Ports Manual Page[/PMAN]
 option

testing the
[THREAD]Problem or Bug Report[/THREAD]
 option

testing the
[COMMIT=]Commit reference[/COMMIT]
 option

testing the
[THREAD]Thread[/THREAD]
 option
 
T-Daemon said:
having to manually set the BBCode
Click to expand...
I never use that WYSIWYG editor, always type the BBCode myself. Much better control and way easier to use. It's become such a second nature for me I even use them in emails at $DAYJOB (where they don't work). I just automatically enter them.
 
You must log in or register to reply here.
Back
Top